Menu
I uploaded my signed apk using the new Google App Signing, and found out I need to change the authentication keys in order for the APIs to keep working. The SHA1 is given directly on the google play console, so I used it successfully with for my Google APIs, however Facebook login key is different (28 characters ending by "=" ). Since I don't know the alias of the new keystore created by google, I don't know how to get this key. Hope someone can help. Cheers,
Q
620
Answers related to “Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again” first, you need to generate a signing key using keytool and create keystore file for your project.
Open Play Console and go to the Play App Signing page (Release > Setup > App integrity). If you haven't already, review the Play App Signing Terms of Service and select Accept.
Android requires that all APKs be digitally signed with a certificate before they are installed on a device or updated. When releasing using Android App Bundles, you need to sign your app bundle with an upload key before uploading it to the Play Console, and Play App Signing takes care of the rest.
When you use Play App Signing, you can either upload an existing app signing key or have Google generate one for you. Keep your app signing key secret, but you can share your app’s public certificate with others. Upload key The key you use to sign your app bundle before you upload it on Google Play.
When you use Play App Signing, your keys are stored on the same secure infrastructure that Google uses to store its own keys. Keys are protected by Google’s Key Management Service. If you want to learn more about Google’s infrastructure, read the Google Cloud Security Whitepaper. Android apps are signed with a private key.
App signing key The key Google Play uses to sign the APKs that are delivered to a user's device. When you use Play App Signing, you can either upload an existing app signing key or have Google generate one for you. Keep your app signing key secret, but you can share your app’s public certificate with others.
When you use a Google-generated key, Google automatically generates a cryptographically strong RSA key that’s 4096 bits. If you choose to upload your own app signing key, then it must be an RSA key that’s 1024 bits or more. Instructions for apps created before August 2021 Step 1: Configure Play App Signing
Thank me later
echo YOUR_HEXADECIMAL_KEY | xxd -r -p | openssl base64
Just found out by myself. Actually for Facebook Login, you just need to translate the hexadecimal code of your SHA1 into Base64. You can find some online tools to do it. Hope this helps someone someday =)
35
Just to add another option, one can check the device's logcat & there's a Log from Facebook Sdk with the "key" expected/required to login, we can directly copy+paste from there as well instead of converting it through an online tool.
2
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
