Android Question Google Play Console: "App Bundle is signed with the wrong key". But it's not!

[Lucian Gontila]

I'm trying to upload a new version but keep getting this error:

"Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your App Bundle is expected to be signed with the certificate with fingerprint:

SHA1: ED:91:7C...

but the certificate used to sign the App Bundle you uploaded has fingerprint:

SHA1: 7B:EC:70...".

I have multiple keystore files for various apps but I'd checked them and none of them has SHA1: ED:91:7C... so it's not about using the wrong key.

I have uploaded a previous version of the app just 4 days ago and everything worked just fine. I've just updated to v13.40, latest commandlinetools-win, resources, android-36 and jdk-19.0.2.

Please can you tell me what is wrong and how can I solve that?

 

[CaptKronos]

This has just happened to me as well. Though the last time I updated the problem app was last year and I, too, have updated to v13.40. I have successfully updated other apps but the difference with the problem app is that I opted in to "Play app signing".

EDIT: Ignore the above, it was my mistake, I was using the wrong "#SignKeyFile:".
Lucian, you say you have multiple keystores, I would suggest you double-check that you are using the correct one because the error message you are getting is exactly the same as the one I received.

 

[Lucian Gontila]

This has just happened to me as well. Though the last time I updated the problem app was last year and I, too, have updated to v13.40. I have successfully updated other apps but the difference with the problem app is that I opted in to "Play app signing".

EDIT: Ignore the above, it was my mistake, I was using the wrong "#SignKeyFile:".
Lucian, you say you have multiple keystores, I would suggest you double-check that you are using the correct one because the error message you are getting is exactly the same as the one I received.

Thank you for your reply!
I've mentioned that i've checked the SHA1 required and didn't matched any of the keys...
To make sure, I signed the app, one by one, with all three keys and tried to upload it to the Google Play Store. The result was the same. From what I understood, it asks me to sign the app with an "upload key" that the Google Play Store generated.
I started the key change operation and reset that "upload key". I have to wait 48 hours and I will try again.

 

[Lucian Gontila]

The problem was solved after I've replaced the key with another one that I'm using in a newer application and that is generated a few days ago (the old one was generated almost 10 years ago).
I've replaced it in B4A and operate changes in:
Google Play Console -> Test and release -> App integrity Play app signing -> Settings -> Request key upgrade (Attention! This can be done once annually).
After that I've requested an upload key reset (also in the same Google Play Console page). It tooks 48 hours to reset.
Now everything works again