Android Question The Android App Bundle was not signed

[ilan]

hi

i wanted to upload an update but i am getting this error:

The Android App Bundle was not signed.

everything worked fine last week.
what could be the problem?

 

[Giovanni_C]

The page on my console just ask to load an app bundle. If I try to load an apk I get this message that says to load a valid app bundle:

Anyway, I opened a ticket on googleplay-developer-support@google.com

 

[Giovanni_C]

As soon as I get an answer from Google I'll update this thread... I'm pretty sure it is something wrong on their side

 

[Turkan Ergin]

Which error did you get? I was able to upload an APK here.

When I want to install APK I get this error "Install a valid application package"

 

[tuhatinhvn]

It looks like you can upload an APK even if you previously uploaded an AAB. Try it as a temporary solution.

I try with APK but google play console dont allow it, it notice not valid package

 

[Erel]

1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:

#SignKeyAlgorithm: -digestalg SHA-256 -sigalg SHA256withRSA

3. If you are using an old key then submit an APK instead of AAB. There are no advantages for AABs.

 

[tuhatinhvn]

1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:

#SignKeyAlgorithm: -digestalg SHA-256 -sigalg SHA256withRSA

Does it work?

OKKK! It works now
This is solved!

 

[Erel]

Great. Looks like they silently changed the requirements.

If you are using an old key then you can probably still upload an APK instead of AAB.

 

[Erel]

This change will be applied internally in the next update.

 

[tuhatinhvn]

Great. Looks like they silently changed the requirements.

If you are using an old key then you can probably still upload an APK instead of AAB.

I only tested with new app, may be need more check with old app when i need updated

 

[ahpiuma]

1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:

#SignKeyAlgorithm: -digestalg SHA-256 -sigalg SHA256withRSA

Does it work?

The last solution proposed by Erel worked for me.

 

[Turkan Ergin]

Great. Looks like they silently changed the requirements.

If you are using an old key then you can probably still upload an APK instead of AAB.

I am very happy to be part of such an amazing group and thank you very much for the speed and dedication to the solution.

 

[ilan]

Which error did you get with an APK?

 

[ilan]

1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:

#SignKeyAlgorithm: -digestalg SHA-256 -sigalg SHA256withRSA

Does it work?

thank you Erel for the fast solution. this solve the issue and i can upload the aab file to google play. ???

 

[Giovanni_C]

1. Check Tools - Private Sign Key. Look for the public key algorithm. If it isn't an old key then it should show 2048-bit RSA key.
2. Assuming that this is the case, add this line:

#SignKeyAlgorithm: -digestalg SHA-256 -sigalg SHA256withRSA

Does it work?

Tested right now. It works perfectly, thank you!!!
About the ticket .... no news from google yet, but I hope it can be useful to let them understand that it could be nice to have warnings about further changes.

 

[tsteward]

After adding #signkeyalgorithm I get this error when compiling aab file

jarsigner error: java.lang.IllegalArgumentException: key algorithm not compatible with signature algorithm

 

[Ferdari]

After adding #signkeyalgorithm I get this error when compiling aab file

Same error here, my cert is the old one from 2018-19, any sugestion @Erel?

EDIT:
Uploaded APK and accepted successfully

 

[Ferdari]

Tested right now. It works perfectly, thank you!!!
About the ticket .... no news from google yet, but I hope it can be useful to let them understand that it could be nice to have warnings about further changes.

Where you set the ticket?, maybe we can join or up-vote to make pressure..

 

[Giovanni_C]

Where you set the ticket?, maybe we can join or up-vote to make pressure..

To open a ticket I click on the question mark in the top right corner of the developer's console. This action opens a guide, and in the guide clicking on "contact us" one has to provide the information needed to open a ticket.
About loading APKs I found this: https://support.google.com/googleplay/android-developer/answer/9842756?hl=en
At the point "How it works--> Note" there is some information. They suggest to use their Play App Signing. Don't know, up to now the key signature generated by B4A works perfect for me.

 

[tsteward]

Same error here, my cert is the old one from 2018-19, any sugestion @Erel?

EDIT:
Uploaded APK and accepted successfully

Surely uploading APK is a patch not a fix yeah?

 

[Erel]

Surely uploading APK is a patch not a fix yeah?

No. There are no benefits for AABs. At least not with B4A. If you want to waste your time and energy then ask Google to upgrade your key (the old key isn't compatible with their new requirements). Eventually the result will be exactly the same.

Bottom line:
1. If using old key - submit an APK.
2. If using new key - add the #SignKeyAlgorithm