I’m a bit of an amateur, so apologies if this comes across as daft.
I uploaded an app to Google Play store a while back, and I saved the keystore and password information associated with that upload so that I could update the app later if need be.
I’m trying to update it now, and despite using the same keystore to build - the SHA1 signatures do not match after I download the build from Expo, and Google Play is not accepting the upload.
Note: I tried to upload images but it would only let me upload one.
So, just imagine that I’ve included screenshots showing that my keystore signature matches the upload keystore signature on google play, but the fingerprint of the .aab file downloaded from Expo after build does not match.
Then, when I try to upload the .aab to Google Play it gives me an error stating that the wrong key has been used.
I’ve exhausted google search on this one, out of suggestions i’ve seen the Name in app.json is unchanged, and the package is unchanged as well. Not sure what’s going on. Anyone have any suggestion for what I might be missing here?
Thanks in advance for any ideas.