FAQ
- Play Services Application Id
- Make sure Game Services capability is enabled when you create your app id manually in iOS developer portal
Each keystore is linked to a SHA fingerprint. Please check below for creating SHA fingerprints on each environment (Debug, Release and Google play)
Debug (Development Mode)
Release (Release Mode)
Google Play Store (Alpha/Beta/Production)
When development mode is enabled in Build Settings on Unity, it always uses defualt debug.keystore.
Command for getting SHA fingerprint
keytool -list -v -keystore "PATH_TO_DEBUG_KEYSTORE" -alias androiddebugkey -storepass android -keypass android
Check the below table to get PATH_TO_DEBUG_KEYSTORE (debug.keystore)
Platform | Path |
Windows | C:\Users\USERNAME\.android\debug.keystore (Replace with your username in the above path) |
MacOSX | ~/.android/debug.keystore |
SHA fingerprint to consider finishing the configuration on google play console
When development mode is OFF its considered to be in release mode. And unity uses the keystore you set in the player settings.
Command for getting SHA fingerprint
keytool -list -v -keystore "PATH_TO_KEYSTORE" -alias ALIAS_NAME -storepass STORE_PASSWORD -keypass KEY_PASSWORD
PATH_TO_KEYSTORE : This is the path of the keystore you created for your app.
Use your release keystore along with providing. ALIAS_NAME, STORE_PASS and KEY_PASS
Once you upload your apk to play console, you are given an option to let google sign your apk. This is usually called google play signing and its recommended to enable it.
Once your app is ready for testing through testing tracks(Alpha/Beta) or production, you need to add the SHA fingerprint once your app signs with google play signing. You can fetch this fingerprint by following below steps
- 1.
- 2.Select Setup and click on App Signing. Under App signing key certificate copy the value of SHA-1 certificate fingerprint
- 3.
Google play app signing SHA fingerprint
This usually happens for one of the 3 main reasons.
- 1.Your package name and certificate fingerprint do not match the client ID you registered in Developer Console. This means you haven't added the required SHA fingerprint correctly. You need to copy the printed SHA1 fingerprint in the logcat log and add it in the credentials section of google play console.
- 2.
- 3.In sandbox mode, the user you are trying to login is not added as a tester in your App's google play console under Play Games Services -> Setup and Management -> Testers
Nearly 99% of the sign in errors are due to not adding the correct credential for the keystore that is used in Google Play Console-> Your App -> Play Games Services -> Setup and Management -> Configuration.
For logging in successfully, you need to create the credential by setting the right SHA fingerprint on google play console. Please check setup here.
You can use the below command for getting the SHA fingerprint quickly
keytool -printcert -jarfile PATH_TO_APK_FILE
You need to have your JAVA_HOME environment variable set on windows or java should be in the PATH on mac.
keytool is a program from java sdk and you need to have java setup correctly to get it detected. Its used for getting SHA fingerprint from keystore or an APK.
This is an issue at iOS level which we don't have control. It's a limitation with Game Center and it won't show up the sign-in prompt once user cancels it earlier.
To resolve, user needs to manually sign-in from the settings of his device.
Last modified 1yr ago