Now, I am even more confused because I already asked the google team to reset my key
I followed these instructions, after having downloaded my .jks file from expo server
// email from Google
Here’s how to generate and register a new upload key:
Follow the instructions in the Android Studio Help Center to generate a new key. It must be different from any previous keys. Alternatively, you can use the following command line to generate a new key:
keytool -genkeypair -alias upload -keyalg RSA -keysize 2048 -validity 9125 -keystore keystore.jks
This key must be a 2048 bit RSA key and have 25-year validity.
Export the certificate for that key to PEM format:
keytool -export -rfc -alias upload -file upload_certificate.pem -keystore keystore.jks
Reply to this email and attach the `upload_certificate.pem` file.
I’m not sure what you need to do exactly, but a certificate is just the signed public key, basically. You also need the private key so that you can sign the app. I’m not sure where you get the private key from if Google has reset it.
I see that under the section where you downloaded the cert it says:
If you have lost your upload key, please contact our support team.
I believe that is what you will need to do.
If that’s what you have already done, then what did they require of you? I assume they would have asked you for the certificate and you should still have the corresponding key.
Sure I meant that I am not sure what is wrong/what you need to do to fix the problem.
OK. How did you fetch the keystore from Expo? And are you using EAS Build or the classic build system? (I believe these have potentially different keystores if your app was migrated from the classic build system to EAS Build.)
Maybe verify that the SHA1 checksums for the key/cert match what Google is saying they’re getting?
> Enter keystore password:
> Keystore type: JKS
> Keystore provider: SUN
>
> Your keystore contains 1 entry
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, 13 Feb 2022, PrivateKeyEntry,
> Certificate fingerprint (SHA-256): 84:79:0E:E6:FF:18:14:F6:E5:48:F2:1C:EA:5E:6C:A5:F7:D1:3D:E9:BD:56:8E:A5:18:F9:94:39:84:AB:73:0E
>
> Warning:
> The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore @wodin__deps-keystore.bak.jks -destkeystore @wodin__xxx-keystore.bak.jks -deststoretype pkcs12".
So it seems it’s stored in “JKS” format rather than “PKCS12” format.
What format is your keystore in? And if it is in “PKCS12” format, does it make any difference if you convert it to “JKS” format?
The cert is still the same. You should not have had to send it to Google again.
One thing I am suspicious of:
Your Subject and Issuer are filled with “Unknown” which seems unlikely to be right. Normally, for an SSL/TLS certificate (which I am more familiar with) these would contain the host name, organisational unit, organisation, city, province/state and country. But maybe it’s fine like that, because after all, Expo doesn’t ask for that info when creating certs automatically.
I meant that I am not sure what is wrong/what you need to do to fix the problem.
wait until it’s approved
