In order for Google Sign-in (and all related Games Services features) to work, I had to correct the fingerprint for my pre-existing OAuth2 Client ID (the one that I created before publishing my app). You can verify this fact from: Google Play Console -> Games Services -> Select your App -> Games Details -> API Console project -> Credentials -> OAuth 2.0 client IDs The one that you created before publishing your app (and before enabling google signing), which is indeed the "right" one.Ī NEW one created by Google when you enabled Google Signing. The conflict with this situation, is that you may end up with two OAuth 2.0 client IDs: The new one generated by Google when you enabled Signing (the "signing certificate"). The one coming from your local keystore (keytool -exportcert -keystore path-to-production-keystore -list -v), known as the "upload cert". If you enabled "Google Play App Signing" when publishing your app, you are now probably dealing with two fingerprints:
If asked for password enter your signed apk keystore password. Google / firebase SHA-1 : keytool -exportcert -keystore path-to-debug-or-production-keystore -list -vįacebook release key hash: keytool -exportcert -alias -keystore | sha1 -binary | base64 Use this link or copy the key hash provided by facebook loginĬreate / use Keystore details of signed apk. Integrating google sign in (change SHA-1 of OAuth client),įacebook login (change key Hash (generate key hash using SHA-1 Provided by google play where ever you used it before. You need to change uploaded certificate details with new details Then you can see two types of certificateġ- Upload certificate ( your app certificate provided when generating signed apk)Ģ- App signing certificate ( because you enabled Google Play App Signing, so they provided new certificate details for your published apk) certificate details in respective places.Ģ) You provided debug key store / SHA-1 certificate details instead of RELEASE certificate detailsģ) error while generating certificates. Then your Upload certificate details will change and you need to rewrite SHA-1 etc. Google Play App Signing is enabled for this app. 1) when you create / publish an app through google play console, there is an option for enable Google Play App Signing.
0 kommentar(er)
