Play store key invalid

[Bob_The_Cow_Inc]

I bundled my app as a aab and uploaded it to the play store. It gives me 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: B4:0E:11:F3:4F:AE:20:74:5F:02:AA:8A:CA:9E:B2:EA:52:40:B0:B2
but the certificate used to sign the App Bundle you uploaded has fingerprint:
SHA1: 7A:53:6B:F8:29:E6:94:A4:BF:BB:8D:81:54:46:56:00:2D:43:E6:2F

Please help!

[Bob_The_Cow_Inc]

Can someone please help me with this?

[Anke]

Signing an AAB with a wrong keystore - error from Play Developer console

Was the app (the AAB update) built with the same builder? Has the keystore been deleted, overwritten or changed in the meantime. If yes, is there a backup of the old (original) keystore (android.keystore) that the app was signed with before/from the beginning?

---

https://community-appinventor-mit-edu.ezproxy.canberra.edu.au/search?q=signed%20with%20the%20wrong%20key%20order%3Alatest

[Bob_The_Cow_Inc]

The app was built with the app inventor and I did not mess with the key store. Does this have something to do with googles signing. I don't really understand about how they insist they sign your apps for you but then make you sign your apps to upload them?? How do I sign it correctly?

[Anke]

Have you changed the way you sign, so did you recently switch to Google App Signing? If so, why?

[Bob_The_Cow_Inc]

I was able to fix it by deleting the app and starting a new one. The app bundle successfully uploaded then.

[Anke]

@Bob_The_Cow_Inc

I was able to fix it by deleting the app and starting a new one.

Explain this in more detail as no one else - including me - understands it.

[Bob_The_Cow_Inc]

I deleted the app draft (not just the release) in Google Play, and then started a new one. I uploaded a aab file again and there were no issues.

[Anke]

Ok, but I don't understand why deleting an app draft in the Play Developer Console and creating a new app would fix the (supposed) problem. So there must have been another problem with the old (deleted) app. Anyway, let's leave it at that.