App signing error when uploading AAB-file to Google Play Console

[Henrik R.]

Hi!

According to the guides I have read, you can still let Buildozer sign your Android Kivy app automatically - see https://gist.github.com/Guhan-SenSam/fa4ed215ef3419e7b3154de5cb71f641 or https://github.com/Android-for-Python/Android-for-Python-Users#release-builds .

But when I upload the resulting AAB-file Google Play Console says:

"To upload an Android App Bundle you must be enrolled in Play app signing."

So what do I do now?

[Henrik R.]

Do I simply opt in on Google Play app signing in the Google Play Console?

Will the app be 'double signed' in that way?

[Henrik R.]

In that case:

I have to choose between 3 ways to upload my key. Which do I choose?

"Use existing app signing key from Java keystore"?

[Henrik R.]

Solved:

Yes - I just had to opt in to Google Play App Signing and choose "Use existing app signing key from Java keystore".

I had to 'decode' this command:

$ java -jar pepk.jar --keystore=foo.keystore --alias=foo --output=encrypted_private_key_path --encryptionkey=[deleted]

Into this:

$ java -jar pepk.jar --keystore=<path+filename of your key file> --alias=<key alias> --output=<path+filename of new key file> --encryptionkey=[deleted]