Android Tutorial App Bundle - Steps to updating Existing App (apk to aab)

mcqueccu

Well-Known Member
Licensed User
This Tutorial is for those who already have an existing application in the play store that is APK and want to switch to App Bundle (AAB) which will become compulsory in August 2021.

Steps for updating the EXISTING application to App bundle (Switching to App bundle)

1. Make sure you are using the latest B4A version (Current version 10.7)
2. If possible, Redownload the 2 files in step #2 here https://www.b4x.com/b4a.html
3. Download bundletool.jar and put it in <android sdk>\tools\bin
4. Select Release or Release Obsfucated in the IDE.
5. Goto Project -> Build App Bundle (the AAB file will be created in the objects folder)
6. Create a new Release in play store and Upload your new AAB File
 

GMan

Well-Known Member
Licensed User
Cant get the bundletool.jar - causes an network.error
can you zip it ?
 
Last edited:

GMan

Well-Known Member
Licensed User
Thx - now it works
But have to try it several times
 

ArminKh1993

Active Member
This Tutorial is for those who already have an existing application in the play store that is APK and want to switch to App Bundle (AAB) which will become compulsory in August 2021.

Steps for updating the EXISTING application to App bundle (Switching to App bundle)

1. Make sure you are using the latest B4A version (Current version 10.7)
2. If possible, Redownload the 2 files in step #2 here https://www.b4x.com/b4a.html
3. Download bundletool.jar and put it in <android sdk>\tools\bin
4. Select Release or Release Obsfucated in the IDE.
5. Goto Project -> Build App Bundle (the AAB file will be created in the objects folder)
6. Create a new Release in play store and Upload your new AAB File
Will AAB signed with signkey which is generated by b4a right?
But why erel said we need to extract privatekey for existing apps at this thread https://www.b4x.com/android/forum/t...7-build-app-bundle-feature.128323/post-805117
and for new apps just create a new signkey by keytool
 
Last edited:

mcqueccu

Well-Known Member
Licensed User
Will AAB signed with signkey which is generated by b4a right?
Yes, AAB will be signed with existing B4A keys.

But why erel said we need to extract privatekey for existing apps at this thread https://www.b4x.com/android/forum/t...7-build-app-bundle-feature.128323/post-805117
and for new apps just create a new signkey by keytool
It depends on WHEN the existing app is uploaded.

1. If the Existing Application is submitted BEFORE the change in the play console dashboard. Then you DON'T need to extract the privatekey before you can upload.
Just go to create New Release and You should see something like this - Release signed by Google play.

Upload your AAB signed with B4A keys and it will work.

1616996171265.png



2. If the Existing Application is submitted AFTER the update to the play console dashboard, using the opt-out option. You will need to Extract the private key using PEPK.jar
With this, when you create a New Release, you should see OPT-IN.
When you click the Optin then you can upload your extracted Private Key.
 

ArminKh1993

Active Member
Yes, AAB will be signed with existing B4A keys.



It depends on WHEN the existing app is uploaded.

1. If the Existing Application is submitted BEFORE the change in the play console dashboard. Then you DON'T need to extract the privatekey before you can upload.
Just go to create New Release and You should see something like this - Release signed by Google play.

Upload your AAB signed with B4A keys and it will work.

View attachment 110621


2. If the Existing Application is submitted AFTER the update to the play console dashboard, using the opt-out option. You will need to Extract the private key using PEPK.jar
With this, when you create a New Release, you should see OPT-IN.
When you click the Optin then you can upload your extracted Private Key.
Thank you, I think I fully understand what the story is 😘
 

GMan

Well-Known Member
Licensed User
Works great
 
Top