Android Tutorial Publish New App to Google Play

1. Click on button "Create app".
00.png


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


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


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


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


6. After each section, return to the Dashboard.
09.png


7. Next, provide information for store listing.
32.png


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


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


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


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


12. Then use B4A to build the App Bundle.
1614076659519-png.108598


13. Wait for the aab file finished compile.
81.png


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


15. Complete the Release details and submit for review.
84.png


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


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


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


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

mcqueccu

Well-Known Member
Licensed User
Longtime User
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

Expert
Licensed User
Longtime User
Thanks aeric.

The links to the images are broken
 

josejad

Expert
Licensed User
Longtime User
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

Expert
Licensed User
Longtime User
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

B4X founder
Staff member
Licensed User
Longtime User
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

Expert
Licensed User
Longtime User
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.
 
Top