Keystore issues with android app update


We aren’t able to update our app on Play Store because of the keystore issues mentioned below. At the time of first update we created the build with the same expo account and let expo handle the keystore. Now when we try to create a updated build and try to upload that to play store we get the error message different keystore to previous apk

Upload failed
You uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ SHA1: *************************** ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: *************************** ]

Same keystores but different SHA1 fingerprints

hi @devconnecpath, you’ll want to sign your apk with the same keystore that you had in your previous apk. Did you recreate the keystore at some point?

closed #3

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.