Hi
I have an App on Google Play. This app has been available in the store since 2006, it has more than 100k installation.
Now I did an update using the expo and gave the following error.
“You have submitted an APK signed with a different certificate than the previous APKs. Use the same certificate. Your APKs are already signed with certificates with the following fingerprints:”
However I used the command expo build: android -c to send the old certificate, how should I proceed.
Can you try providing this keystore again with EXPO_LEGACY_API=true expo build:android -c? Check before and after output of expo fetch:android:hashes after change hash should match value from play console.
If this won’t help try using expo credentials:manager
Hey elton & juan, would you mind confirming whether the problem persists after upgrading expo-cli to the latest version? We’d like to fix the issue for others if possible.
We ran into this issue with a new app (re-using an old key). We also had to do expo credentials:manager and upload the keystore there. otherwise expo kept creating its own keystore, even when we provided one during build.