AAB file signing tutorial

I agree with you, but the guide explains the process required for both existing and new applications

In addition, I can confirm that even after registering for PAS the APK can still be used

For new apps (i.e. for AABs) you just have to make sure that a new keystore is used. That's all.


no es muy descriptivo el manual, a partir del paso 5 no es muy claro

As I already explained before, there is no need to follow this guide.

So what is your suggestion for new apps, which require aab to keep it as simple as possible?
As we know, for already uploaded apps before August 21 we can continue to upload apks...


As I already said:

Then before creating a new keystore let me suggest to first backup the old keystore because for the older apps you still might want to use it...


1 Like

Yes, definitely!


I'm afraid I don't understand steps 5 or 6.

Have you seen this post?

Yeah, I saw it. I don't understand it.

You don't have to understand because it isn't necessary.

It is if I want to make my new version of my app an Android Bundle which I do. I know I don't have to. I've decided I want to. I'm trying to distinguish my stupid product in a over-crowded field of equally-stupid products. It may not work. I want to try it.

Look, you're not helping. Stop. Just stop.

Ok, if you want to make your life harder than necessary, go ahead ... :upside_down_face:

1 Like

did u need help with that?

Hi i need help for this part:

the path to export the private key file (what needs to be uploaded to Play App Signing) It should be a zip file!

what does this mean and what am I supposed to do

The path should be as follows: …./download/keyfile.zip
The file will be created in a downloads folder with the name: keyfile.zip

I just managed to upload and sign my first AAB file. I could not find a way to avoid the signing step on Google PlayStore.

Step 1: Download AAB file (Build -> AAB)
Step 2: Download your signing key (Project -> export keystore)
Step 3: During AAB upload on PlayStore, when you reach the step "Export and upload a key from Java keystore", enter this (replace with your paths where necessary):

D:\AI2\GooglePlay>"C:\Program Files\Java\jdk.java.net\21\jdk-21.0.2\bin\java" -jar pepk.jar --keystore=android.keystore --alias=androidkey --output=output.zip --include-cert --rsa-aes-encryption --encryption-key-path=encryption_public_key.pem

Enter password for store 'android.keystore': android
Enter password for key 'androidkey': android

Note: "C:\Program Files\Java\jdk.java.net\21\jdk-21.0.2\bin\java" is the path to Java on my computer, which is downloaded as a ZIP file and extracted. The ZIP file is from here: https://jdk.java.net/ (I chose "JDK 21"). The reason for doing this is that the "normal" Java installation did not work, which was explained on stackoverslow ( android - 'Cannot find any provider supporting RSA/NONE/OAEPWithSHA1AndMGF1Padding' when trying to enroll to 'Let Google Play manage your app signing key' - Stack Overflow )

Note: pepk.jar and encryption_public_key.pem are provided by Google PlayStore. These two files, as well as file android.keystore (from Step 2) are in one and the folder in my case.

Step 4. Upload output.zip to GooglePlaystore at step ""Export and upload a key from Java keystore"

16 posts were split to a new topic: Signing an AAB with a wrong keystore - error from Play Developer console

A post was merged into an existing topic: Signing an AAB with a wrong keystore - error from Play Developer console