I’ve just built an aab bundle from expo, and I’m receiving this error when uploading the aab bundle onto the 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: —MY SHA KEY HERE—
I checked my current sha key by executing this command:
expo fetch:android:hashes --config ./app.json
and the output in Google Certificate Fingerprint: matches the key mentioned in play console.
What is wrong here?
One thing to note here is, I just updated my expo version from v37 to v40 in an incremental manner.
you maybe renamed your app slug or built it with a different username between when you last submitted the app and now. keystores are assigned to a specific username/slug combination.
well, something happened to change the keystore that your app is using! i was just suggesting the most common things. another possibility is someone ran expo build:android -c or expo build:android --clear-credentials or ran expo credentials and removed the keystore.
if it’s not one of those things, then the only remaining possibilities would be that google changed the upload keystore (highly unlikely) or on expo servers we changed your keystore without you requesting it (no known instances of this occurring, highly unlikely).
you can verify that you used the same username and slug by finding your most recent build you submitted to the store on expo.io and verifying that the username and slug is what you expect.
If, it is necessary to update the keystore on Expo, I did that too, but received the following error: Error: Invalid JKS Keystore: Invalid keystore format
I have resolved the problem.
My approach: Download the upload certificate from expo servers, and share the same with the Google Support, requesting them to update with the new PEM file.