I am heaving trouble into upload apk into play store, since I lost the certificates.
It’s saying certificate fingerprint issue.
What I did
expo build:android --clear-credentials , I created .jks file from this.
Now I created .pem file(upload certificates) from this expo fetch:android:upload-cert
I gave this to google to upload this certificates, since my app was enable for the App Signing. Google uploaded successfully and then ask us to upload the app with the same certificated.
I created the APK again from “expo build:android --clear-credentials”, I choose the option 2 “select my own certificates”.
I set all the details
And yeah I got the App on Expo account into build section.
I download the app and upload into the App release , It’s the same issue that upload faild with reason “You uploaded an APK that is not signed with the upload certificate. You must use the same certificate. The upload certificate has fingerprint:”
I was wondering that where I did wrong , I am doing first time with Expo, I created many app into react native and upload it.
But from Expo doing first time, so I follow the right steps for that, again Play store denied my APK.
They also gave some command in the approval process to map .pem file. keytool -export -rfc -alias upload -file upload_certificate.pem -keystore keystore.jks
But I did from the expo fetch:android:upload-cert
Please please let me know I am stuck into this.
Check hashes in “App signing” tab in app store and compare them with output of expo fetch:android:hashes. If you have keystore somwhere locally check it using keytool keytool -list -v -keystore path_to_keystore -alias key_alias
After those 3 steps you listed your app should build with correct credentials, but if I read you correctly you ran clear credntials after that again?
How did you get that keystore you used when specifying credentials manually? if you used fetch:android:keystore specify after which step you did that?
Thank you for the reply,
I have only one JKS now.
And I compare that SHA-1 certificate fingerprint, this is not the same as what we have it on “App signing” tab in Play Store.
I didn’t did this one because I have already the password and .jks when I run this expo build:android --clear-credentials
I keep all this into another folder and doing all the time expo build:android --clear-credentials
then 2) I want to upload my own keystore!
I gave the path and enter all detail into the CLI
Is this the mistake I did , I should run after **expo build:android ** only , this will signed with the same certificates I used for.
This expo build:android --clear-credentials will clear the details from expo server as well ?
So since I have only 1 .jks for now, I think this will not work.
I need to generate it again and and create new .pem file and send again to Google to update the key.
Is it or somthing in EXPO can handle this.
I keep the files and all credential before all well into two other places, but I don’t know what happened.
I really take care of this time again, so make all the files and credentials separately
Actually I requested for the two app before and the same issue for the two apps.
I again apply into the google support for both two app now, I’l give the upload certificates .pem file which we generated from
Thank you for your support.
I’ll get back to you on this again when it works as soon as google approve this.
Can you do me a favour, I want to do Android App Bundles in expo for my both app, so when I do this command expo build:android -t app-bundle
This will build an APK with Android App Bundles, I want to reduce size of the app, also play console suggest the same.
Can you let me know on this and also this will change the .jks again