Android Tutorial Publish New App to Google Play

1. Click on button "Create app".

2. Enter your App name. Select App or Game.

3. Scroll down. Check all the declarations. Click on button "Create app".

4. Go to Dashboard and continue set up your app.

5. Proceed with App access and other sections. Provide the required information and click on button Save.

6. After each section, return to the Dashboard.

7. Next, provide information for store listing.

8. Upload app icon. The size need to be 512 x 512 pixels.

9. Upload Feature graphic (1024 x 500 pixels) and some screenshots (320 pixels width each).

10. Go to Release -> Production. Note that no option to upload signing key.

11. If you click the link "Change app signing key", a dialog box will be pop up. Click on button "Use Google-generated key".

12. Then use B4A to build the App Bundle.

13. Wait for the aab file finished compile.

14. Back to Google Play Console and upload the aab file.

15. Complete the Release details and submit for review.

16. Proceed to click on button "Start rollout to Production".

17. A confirmation dialog pop up. Click on button "Rollout".

18. The app is now successfully published and pending for review by Google.

Edit: Unnecessary steps have been removed as pointed out by @mcqueccu

 

[mcqueccu]

Thank you for taking your time to list the steps and procedures. It will be very helpful

I think step 12 and 13 are unnecessary.

Using latest B4A IDE, generate new keystore file and you can use it directly to upload and sign your apps.
Also, no need to use #If aab symbol

 

[josejad]

Thanks aeric.

The links to the images are broken

 

[mcqueccu]

Thanks aeric.

The links to the images are broken

I also thought the same but when I refresh couple of times and waited for a like a minute, they started to load

 

[josejad]

I also thought the same but when I refresh couple of times and waited for a like a minute, they started to load

You're rigth, now I see them

 

[aeric]

Using latest B4A IDE, generate new keystore file and you can use it directly to upload and sign your apps.

I see. Thanks. I will try this in the future.
The reason I created the jks file is because I encountered an error. So I thought I need to create a key file.

 

[aeric]

The links to the images are broken

I uploaded the images to Google Photos and copy the image address. Not sure I am doing correctly.

 

[asales]

Thanks @aeric.
The links to images still broken.

 

[aeric]

I think step 12 and 13 are unnecessary.

Using latest B4A IDE, generate new keystore file and you can use it directly to upload and sign your apps.
Also, no need to use #If aab symbol

@mcqueccu You are right! I created a new key which is 2048-bit RSA.
However, since I made the mistake for this app, I have no choice but to use the same jks to compile the aab file for it's updates.
For other apps, I will follow your steps above.

 

[Erel]

The bottom line is:
If you are uploading a new app then create a new key, which you will use from now on, and nothing else special is needed.

If you are updating an existing app then either follow Google instructions or keep using APKs instead of AAB. There are no advantages for AAB packages.

 

[aeric]

The bottom line is:
If you are uploading a new app then create a new key, which you will use from now on, and nothing else special is needed.

If you are updating an existing app then either follow Google instructions or keep using APKs instead of AAB. There are no advantages for AAB packages.

I found one of my old app (last update was 2019) already opt-in so I have no choice but to use the AAB package (maybe there is a bug or mistake by Google).
The other old app I am still able to use APK and has an option to opt-in.
But I am happy I have learned how things work and B4A is great in simplified all the complicated hard works.

 

[aeric]

The links to the images are broken

I have reuploaded the images to forum.

 

[Alex Simonis]

Great guide! Thank you.

 

[Mashiane]

Thank you so much for this. I was just lost now and this came to my rescue.

Just a comment about the App Signing Key, I think you need to mention the option to use the Tools > Private Sign Key just before you generate the aab as you cant generate it without a private sign key.

 

[Mashiane]

Also other things to note:

1. The package name needs to be

2. The target version should be 30+, so means a change in manifest file.