How to get the SHA-256 fingerprint in Unity

Get the SHA-256 fingerprints of the keys that sign your Unity Android build, for Grovs App Links.

Grovs lists your signing certificates' SHA-256 fingerprints in assetlinks.json, so Android can verify App Links. Unity doesn't run a Gradle project you can call signingReport on, so read the fingerprints with keytool.

Register every key that signs your game in the Grovs dashboard under SDK Setup → Android. App Links fail in any build whose key is missing, and the link opens the browser instead.

keytool ships with the JDK. Unity's Android module installs one under its OpenJDK folder. If keytool isn't found, add that JDK's bin directory to your PATH.

Debug keystore

Unity signs builds with the Android debug keystore when Player Settings → Publishing Settings has no custom keystore:

Bash

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android

Copy the SHA-256 line.

Upload keystore

Use the keystore and alias set in Player Settings → Publishing Settings:

Bash

keytool -list -v \
  -keystore /path/to/user.keystore \
  -alias your_alias_name

keytool asks for the keystore password. Copy the SHA-256 line.

Play App Signing key

Apps installed from Google Play are signed with Google's app signing key, not your upload key.

Open the Play Console

Open App integrity

Go to Setup → App integrity.

Copy the fingerprint

Copy the SHA-256 under App signing key certificate into the Grovs dashboard.

How to get the SHA-256 fingerprint in Unity

Debug keystore

Upload keystore

Play App Signing key

See also