Android Question App signing frustration

[Tony Tetley]

I have a new version of an app already in the play store. Play store will not allow me to updoad a new version until I opt=in to app signing.

The .keystore that is create by the B4A private sign key is not accepted when upload the app bundle as not a valid format. I create a private key with the pepk.jar utilith but B4A will not build an app bundle saying the .keystore is TOO big. I am totally confused and frustrated. I am unable to find anything in the forum messages that get me coing.

Any sugestions?

Thanks.

 

[jahswant]

No no and no. Use the normal private key sign to create your key at it will work.

 

[Tony Tetley]

No no and no. Use the normal private key sign to create your key at it will work.

Maybe I have been away from B4A too long. I create a private sign key from the Tools menu. I build app bundle from the project menu. When I try to upload to the play store it says "To upload an Android App Bundle you must be enrolled in Play App Signing." That is what I did before and went the route of the pepk.jar which did not work.

The only tutorial I can find on app signing seems to be out of date.

 

[Tony Tetley]

No no and no. Use the normal private key sign to create your key at it will work.

OK, so I uploaded the .apk instead of the .aab and it worked.

 

[Erel]

OK, so I uploaded the .apk instead of the .aab and it worked.

This is indeed the simplest solution for existing apps, if you don't want to bother with the pepk.jar tool (which is not too complicated as well).

Use APK for existing apps and use AAB for new ones. You won't lose anything.