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

GooglePlay - wrong signing key for app bundle

The solution was a very basic one. I had to clean my project and then rebuild it.

Android Studio was signing my app bundle with the old certificate i was using.

What I did previously is go to Build -> Generate Signed Bundle / APK and i changed the jks file in the file selector to the new upload jks. It seems Android Studio caches the old certificate path and uses it even though I've selected a new one. Might be a bug in AS.

So yeah ... now if I clean the project every time i change the jks file it works, the apk or app bundle gets signed with the proper certificate...

Your Android App Bundle is signed with the wrong key. Ensure that your app bundle is signed with the correct signing key error

Clean the project and rebuild it, Android Studio caches the previous location of the app Key and creates issues, it is a major bug and it happened with me too

OR

Assuming this is the first time you are uploading the app, and not posting an update

Delete the app release draft completely and start over again

Creating New Release and got 'Your Android App Bundle is signed with the wrong key'

The keystore may be versioned if it was committed as part of your project so simply reverting that change would restore the previous keystore for you to use.

Alternatively, you'd need to contact Google and go through the process of establishing your new keystore as the valid signing entity. You can reach out to Google via this form

You'll need to provide a certificate from your new keystore which you can generate with the following command:

keytool -export -rfc -alias prod -file upload_certificate.pem -keystore keystore.jks

---

Related Topics