If it's a new application try signing in again with this template:
java -jar Path to pepk.jar --keystore=Path to keystore --alias=Enter the alias here, usually applications built in Kodular should have the alias: androidkey --output=The path to export the private key file (what needs to be uploaded to Play App Signing) It should be a zip file! --include-cert --encryptionkey=Enter the sequel here (this is already entered in what you copied from the Play App Signing)
Why?
It is not necessary to switch to Google's Play App Signing (PAS) for existing apps that have been uploaded and published as APK. I would advise anyone not to opt for PAS as it just makes things unnecessarily complicated.
You don't have a choice for new apps, but then there is no problem with signing the AAB.
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...
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.
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):
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"