Android App Bundle is signed with the wrong key issue on Google Play Store

Question

Hi,

I encountered the following problem while attempting to update my previous release of a Xamarin App on the Google Play Store.

"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: 13:7D:76:25:DF:99:1C:19:99:2C:C3:37:5F:E9:DD:35:13:51:DD:CE

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

SHA1: B0:88:10:5E:58:71:AD:C3:32:DD:BC:67:0C:69:49:56:37:02:23:53"

Some time ago, I had to uninstall Visual Studio 2022, and now, when I attempt to update my Xamarin build, I encounter the issue mentioned above.

Attaching a screenshot for help.

Kindly offer a solution to the problem mentioned above.

Thanks,

Answer 1

Hello Sanjay,

Thank you for reaching out in Microsoft Q&A.

This issue typically occurs when the signing key used to sign your app bundle does not match the key that was used for a previous release of your app. Here's how you can resolve this problem:

1. You need to locate the keystore file that was used to sign the previous release of your Xamarin app. It's crucial to use the same keystore to sign updates.
2. Double-check the keystore's SHA-1 fingerprint to ensure it matches the fingerprint mentioned in the error message:

      SHA1: 13:7D:76:25:DF:99:1C:19:99:2C:C3:37:5F:E9:DD:35:13:51:DD:CE
   

3. If you have the correct keystore, you can re-sign your Android App Bundle (AAB) using the following command:

      jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore your_keystore.keystore your_app.aab alias_name
   

   Replace your_keystore.keystore with the path to your keystore file, your_app.aab with the path to your Android App Bundle, and alias_name with the alias you used to sign the app originally.
4. After re-signing the AAB, upload it to the Google Play Console as you would for any other update.
5. Update Google Play Console Settings: In the Google Play Console, make sure your app's signing key information matches the keystore you used to sign your AAB. You can check this under "Release Management" > "App signing."

Note: If you found this response helpful, please acknowledge it to help others facing similar challenges.

Best of luck!