Beginner-friendly Android app publishing procedure, struggling for the first release⁈

First Android app release

After overcoming the copyright barrier (see Last article on Android), the production of the Android application is finally finished. To prepare to publish the app at once ... However, since it was released for the first time, various difficulties awaited: fearful:

I will introduce the procedure of publication, the part that is easy for beginners to get caught, and how to solve it. I also introduce easy-to-understand articles that I referred to when publishing. If you prepare well and know the procedure well, you should be able to do it without problems: thumbs up_tone2: Please refer to those who are thinking about releasing the application from now on, especially those who are new to it.

How to publish your Android app to the Goole Play Store

The following ** 3 steps ** are required to publish the app.

1. ** Google developer registration **
2. ** Create aab file (Android App Bundle) **
3. ** Log in to Google Play Console **

However, it's a good idea to ** configure your app for release ** before entering this step.

Release app settings

Set it as a release app before entering the app publishing step.

Android developer(Preparing for release|Android developer| Android Developers) Is the best to read... As a beginner, I had a lot of things written on it, and I didn't know what to do after all: cold_sweat: So here's what I did before the release.

--Turn off logging and debugging The Log method is a method for developers to record for research purposes, so it is not necessary for user apps, so delete it.

--Set the version information of the app

1. Google developer registration

Steps to finally publish here 1. Developer registration with Google. Developer registration itself is not difficult

I registered by referring to the following article: point_down_tone2: Android developer registration method 2019 latest version easy method

What you need to register as a developer

-** Google account ** (If you don't have one, you need to create one. The account I usually use is fine, but I created a ** new account for development . ) - Credit card ** (to pay $ 25 as registration fee)

2. Create aab file (Android App Bundle)

After registration is complete, it is time to create the aab file.

The creation procedure was written in the Qiita article, so please refer to it: point_down_tone2: Publish the app to the Google Play Store

I had the hardest time creating the aab file here.

I summarized below where I got caught ↓

--I chose APK instead of Android App Bundle

You can create a file with APK, but you will get the following warning when releasing it on Goole Play Console.

** Choose the Android App Bundle **.

--What is the Key store path?

As you proceed, you will see a screen like this. I'm not sure what I'm setting up here, so I'll give you an explanation.

Alias = Upload Key: The key used to sign the App Bundle or APK before uploading for Google Play app signing.

--A warning about the keystore appears

I filled in the required items and created the key. When I pressed OK to complete, I got the following warning.

I was able to remove the warning and make it as it is, but if you want to know the solution, please refer to the following article: point_down_tone2: https://qiita.com/koichi-ozaki/items/c515ba6711811aac44a2

--Cannot Build

When I finally pressed the Finish button, I came to the point where the aab file was completed ... but I can't build at the very end ...

The cause was collaborating on GitHub, so the SDK path was owned by someone else. I solved it by pressing the image mark on the upper right of Android Studio.

If you're creating the app by yourself, it's okay, but if you're collaborating on GitHub, be careful.

3. Log in to Google Play Console

Those who have completed the aab file ... Congratulations: clap_tone2: One more step. The final step is to log in to the Google Play Console. Now publish to the store.

There is a continuation of the article I referred to when I created the aab file earlier: point_down_tone2: Publish the app to the Google Play Store

** What you need to publish the app **

--Aab file created earlier --Screenshots (4-8) --Feature graphic (width 1024 x height 500 image)

I needed a landscape image called a feature graphic (the first thing a user would notice when opening an app store listing). If you prepare it in advance, you can publish it smoothly.

The last hardship here is ... In my case, I created it with an APK file first, so I got a warning when uploading. (There is no problem if you make it with aab file.) So, if you recreate it with an aab file and upload it, a new problem will occur ... I have made version 1 with APK, so I had to change the version.

Select build.gradle (Module: app) and It was solved by raising the Version Code.

After registering the basic information in the Google Play Console, the publication is complete: bangbang: All you have to do now is wait for the app to be published. It's exciting: relaxed:

The memorable first app has been released !!

It took me about 3 days to publish the app ... I feel like I've become a full-fledged person when I go to the app release: laughing: There are various improvements, but I hope we can update it as well. One finger: point_up_tone2: I was able to go from keyboard hitting to production and release in half a year.

Published app: point_down_tone2:

: star: App name: Time is money: star: It is a app </ font> that converts wasted time into money </ font>.