The signing report will include the signing information for each of your app's You can also get the SHA-1 of your signing certificate using the Gradle Upload key certificate will be different than the binary distributed by Google Note: When using Play App Signing, the signature of the binary signed by the To get the certificate of an application binary: # APK file Note: When using Play App Signing, the upload key certificate will be different The keytool then prints the fingerprint to the terminal. The default password for theĭebug keystore is android. The keytool utility prompts you to enter a password for the keystore.
alias androiddebugkey -keystore %USERPROFILE%\.android\debug.keystore alias androiddebugkey -keystore ~/.android/debug.keystore Windows keytool -list -v \ To get the debug certificate fingerprint: Mac/Linux keytool -list -v \ To get the release certificate fingerprint: keytool -list -v \ You should get both the release and debug certificate fingerprints. Open a terminal and run the keytool utility provided with Java to get the SHA-1 fingerprint of theĬertificate.
Keytool or Gradle's Signing Report to get your SHA-1. If you're not using Play App Signing, follow the instructions below to use
On the Release > Setup > App Integrity page. You to provide the SHA-1 of your signing certificate so we can create an OAuth2Ĭlient and API key for your app. Certain Google Play services (such as Google Sign-in and App Invites) require
0 kommentar(er)
