Finding SHA256 fingerprint for Android signing keys¶
To setup Android App Links and enable secure connection between SDK and GetSocial API we require SHA256 fingerprints for all signing certificates you use with your Android app.
There are a couple of ways how you can do it: using
keytool, Gradle task added by GetSocial Gradle plugin or from Play Console.
Locate the keystore file that is used to sign the app. Information about a keystore is obtained by running the
keytool.exe on Windows) command from the JDK:
keytool -list -v -keystore <keystore path> -alias <key alias> -storepass <store password> -keypass <key password>
You have to replace
<key password> with your values.
Keytool should output the following text. The SHA256: label identify the respective signature:
Alias name: androiddebugkey Creation date: Apr 16, 2015 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate: Owner: CN=Android Debug, O=Android, C=US Issuer: CN=Android Debug, O=Android, C=US Serial number: 76afa120 Valid from: Thu Apr 16 10:52:27 PDT 2015 until: Sat Apr 08 10:52:27 PDT 2045 Certificate fingerprints: MD5: 0A:D3:7E:80:3D:40:2A:23:89:B9:AB:9C:4B:B6:63:36 SHA1: 89:33:8F:F2:C5:0C:91:08:4A:CF:04:A5:EC:4A:31:80:84:18:0D:D4 SHA256: 91:AC:3E:2F:CB:EF:50:07:2B:E0:D9:8D:8B:C2:42:87:6A:85:02:86:EB:44:84:10:34:02:ED:35:CE:C6:38:47 Signature algorithm name: SHA256withRSA Version: 3
Using Google Play App Signing¶
Google Play introduces App Signing service to manage signing certificates. If you have enrolled to the service:
- Login to the Play Console.
- Select the app you want to configure.
- Go to Setup → App integrity
Copy SHA256 values:
Using GetSocial Gradle plugin¶
GetSocial Gradle plugin adds a helper task
printSigningCertificateSHA256 to print SHA-256 fingerprints for all configured build flavors: