Android Question Where are we up to changing existing apps to Bundles

tsteward

Well-Known Member
Licensed User
My app is an existing app and some time back I tried changing to AAB format but gave up as could not upload pem file
Error: The private key was not properly encrypted or is not a type of key that we support.

Just wondering if this is possible yet and what I need to do. So much info here but it's just not clear.
 

tsteward

Well-Known Member
Licensed User
Hint: The forumsearch is working!
Another hint: There is a Tutorial on how to build aab files!

Yes I know it is working and I know how to use it. And I always hate creating posts because the first reply is always Did you search?

I also had help from Erel (a while back) to create the PEM file which I can't upload. And Erel suggested I start a new thread.
 

mcqueccu

Well-Known Member
Licensed User
 

tsteward

Well-Known Member
Licensed User
I did not saw any reference to another thread.... Thank you for hiding.
Really...there wasn't one because it was a private email . Sorry I wasn't clear didn't think it was necessary just as it wasn't necessary to tell me to use the search feature. All referenced are over 2 months old and I was simply asking if we had progressed as I still can not convert to the new format Google insists we use.
 

tsteward

Well-Known Member
Licensed User
Don I respect you and your knowledge here and willingness to share it. I apologise if I was snippy
 

tsteward

Well-Known Member
Licensed User
Tried following this guide but
Hint: The forumsearch is working!
Another hint: There is a Tutorial on how to build aab files!

Building an AAB file cand be done through the IDE can't it?
It seems my biggest issue at the moment is Google doesn't like my PEM file to sign up for App Signing which some posts say I don't need to do but others do...i think.so confused
 

mcqueccu

Well-Known Member
Licensed User
Tried following this guide but

Building an AAB file cand be done through the IDE can't it?
It seems my biggest issue at the moment is Google doesn't like my PEM file to sign up for App Signing which some posts say I don't need to do but others do...i think.so confused
I have posted the solution in post #4 Have you tried it? It is the procedure for updating existing app to aab, no need for PEPK

If you are UPLOADING A NEW APP, then you need to create a new Keystore File, which you can do with B4A v10.9 beta

or you follow the steps here

 

tsteward

Well-Known Member
Licensed User
I have posted the solution in post #4 Have you tried it? It is the procedure for updating existing app to aab, no need for PEPK

If you are UPLOADING A NEW APP, then you need to create a new Keystore File, which you can do with B4A v10.9 beta

or you follow the steps here

Yes I tried that and it uploaded the AAB file but complained " To upload an Android App Bundle you must be enrolled in Play app signing. "
 

mcqueccu

Well-Known Member
Licensed User
Okay. So to update,
1. Make sure, the same package name is used in the new App
2. Make sure you increase version code by 1
3. Goto Project -> Build Bundle

Then in the Developer Console,
1. Open your Existing Application
2. Click on Create New Release
3. Drag your aab bundle and upload

Let me know if it is successful. Am interested in seeing screenshot from the playstore


If it is not successful, I want to suggest you compile NORMAL APK AND UPLOAD for now. Then we can try the aab after that.
 

mcqueccu

Well-Known Member
Licensed User
Okay. This should keep you on track Now.

1. Click on OPT-IN, you will be presented with 3 options
2. Choose the second option ie Export and upload a key from java keystore
3. Follow the remaining instruction from Step D in the link below and your release will now be signed


When you are done,
You can use the instructions from post#4 to upload the AAB now. cheers
 

tsteward

Well-Known Member
Licensed User
unable to export or encrypt the private key

I had trouble with this before and Erel did it for me. He emailed me the pem file.
Attached image is trying to upload the pem file from Erel.

I get this when I try to create the file myself...i'm doing something wrong.
It asks me for keystore password then asks for b4a password...dont know what to enter here ( i know my keystore password just not b4a password)

C:\>java -jar pepk.jar --keystore=c:\TonysKey.keystore --alias=b4a --output=c:\ --encryptionkey=eb10fXXXXXX
Enter password for store 'TonysKey.keystore':
Enter password for key 'b4a':
Error: Unable to export or encrypt the private key
java.security.UnrecoverableKeyException: Cannot recover key
at sun.security.provider.KeyProtector.recover(Unknown Source)
at sun.security.provider.JavaKeyStore.engineGetKey(Unknown Source)
at sun.security.provider.JavaKeyStore$JKS.engineGetKey(Unknown Source)
at sun.security.provider.KeyStoreDelegator.engineGetKey(Unknown Source)
at sun.security.provider.JavaKeyStore$DualFormatJKS.engineGetKey(Unknown Source)
at java.security.KeyStore.getKey(Unknown Source)
at com.google.wireless.android.vending.developer.signing.tools.extern.export.KeystoreHelper.extractPrivateKey(KeystoreHelper.java:63)
at com.google.wireless.android.vending.developer.signing.tools.extern.export.KeystoreHelper.getPrivateKey(KeystoreHelper.java:35)
at com.google.wireless.android.vending.developer.signing.tools.extern.export.ExportEncryptedPrivateKeyTool.run(ExportEncryptedPrivateKeyTool.java:167)
at com.google.wireless.android.vending.developer.signing.tools.extern.export.ExportEncryptedPrivateKeyTool.main(ExportEncryptedPrivateKeyTool.java:130)
 

Attachments

tsteward

Well-Known Member
Licensed User
Okay figured that out I now have app signing key certificates
 

tsteward

Well-Known Member
Licensed User
Do I have to change/update the sign key in my app?
 
Top