Android Studio only gives me SHA1, I need SHA256

Question

I want to use assetlinks.json for appindexing. I am supposed to use a SHA256 fingerprint, but when I print out the signingReport in Android Studio, I only have SHA1.

Can I use SHA1? If not, how can I get a SHA256 signed app?

Using Manish Jain's answer, I have managed to list only the debug keys. If I put my actual keystore path and jks file in the path:

keytool -list -v -keystore "C:\Users\myself\Keystores\android.jks" -alias mykey -storepass 1password -keypass 2password

A different set of keys come up, which I assume would be the release key set.

The BIG QUESTION is why Android Studio only lists the debug keys when I print out the signingReport from Gradle and why it says Variant: releaseUnitTest, Config: none? Any idea?

score 91 · Accepted Answer · edited Aug 09 '22 at 18:03

91

You can get SHA256 by using keytool using command prompt (windows).

keytool -list -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android

For Mac users:

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

If you have any special characters in your password, you may need to wrap the password in single quotes.

edited Aug 09 '22 at 18:03

TylerH

20,799
66
75
101

answered Feb 17 '17 at 06:24

Manish Jain

2,139
19
15

1

This solution worked, however, I just noticed that it listed only the debug keys. – Immy Feb 17 '17 at 07:42
2

keytool -list -v -keystore "path to release key store" -alias your release alias here -storepass android -keypass android From this I got both sha1 and sha256 – Neri Jun 07 '17 at 15:51
1

For *Macintosh* (the **password** is **empty** for debug) `keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore` – Bernard Agbemadon May 11 '21 at 21:25

MJV · Answer 2 · 2020-03-14T23:50:55.290

49

There is a much simpler and updated method to find it, comes from this answer.

Navigate to the Gradle tab at the right side of Android Studio.
In the list, navigate to the app section and expand it.
In the expanded list, navigate to the Tasks section and expand it.
Again, in the expanded list, navigate to the android section and expand it.
Double-click on signingReport, and find the SHA-256 Fingerprint at the Run box.

You will find your SHA-256 Fingerprint there.

As @quent commented, change your run configuration in the main toolbar to run the debug configuration again.

edited Mar 14 '20 at 23:50

answered Jan 01 '20 at 21:06

MJV

652
5
14

3

However, don't forget to change run configuration in the main toolbar to be able to run debug configuration again. – quent Mar 14 '20 at 22:21
7

If you cannot find the section here mentions, there's an alternative execution: clicks the elephant button `Execute Gradle Task` on the upper left of gradle tab, and then type in `gradle signingReport`. (Or more on-sightly, the `Run Anything` button on the upper right of Android Studio, then type in the same command above.) – Samuel T. Chou Oct 19 '21 at 08:16
1

Step 3: It shows "Task list not built..." – Elmar Sep 06 '22 at 00:27

score 35 · Answer 3 · answered Dec 01 '20 at 19:12

35

Go to the root directory of the project from the terminal and run the below command

./gradlew signingReport

You will get SHA-1, SHA-256, and other details

answered Dec 01 '20 at 19:12

Naga

1,931
4
25
42

I get different SHA-256 for each package I got - how does it help? – chenop Dec 01 '22 at 07:50

score 20 · Answer 4 · edited Aug 09 '22 at 18:04

20

You can get it from the Google Play Console (https://play.google.com/apps/publish). Follow these steps:

Go to your project in GPC.
Expand "Release Management".
Go to "App signing".
Navigate to "App signing certificate".
Copy SHA-256 fingerprint.

edited Aug 09 '22 at 18:04

TylerH

20,799
66
75
101

answered Feb 19 '18 at 15:15

Tincho825

829
1
13
15

I can found nothing like this in the newest GPC no in 2021 :-( – djdance Sep 15 '21 at 06:54
use Play console Search feature to search "Play App Signing", there you find all the public App signing key certificate/fingerprints listed :) – Pratap Singh Jan 03 '22 at 11:15
This answer is obsolete now; the new solution in Google Play Studios can be found in [this other answer](https://stackoverflow.com/a/73296202/2756409) to this question. – TylerH Aug 09 '22 at 18:05

score 10 · Answer 5 · answered Dec 17 '20 at 02:50

10

Navigate to the Gradle tab on the right side of Android Studio
Expand the project name
Expand Tasks
Expand Android
Double click on signingReport

answered Dec 17 '20 at 02:50

Vikram Kodag

485
5
6

score 10 · Answer 6 · answered Jun 03 '21 at 04:43

10

I always find using ./gradlew signingReport effective and good for me.

Just run the command in your project terminal.

answered Jun 03 '21 at 04:43

Stephen Hechio

160
2
7

score 5 · Answer 7 · answered Dec 03 '21 at 20:00

As of 2021, in the latest Android Studio:

Navigate to the Gradle tab on the right side of Android Studio.
In the list, navigate to the app section and expand it. If you see the Tasks section in the expanded list, then follow this answer and you are good to go.

If you are not able to see the Tasks section then the alternate is:

Click the elephant button Execute Gradle Task on the upper left of the gradle tab, and then type in:

gradle signingReport

and it will print the SHAs in the console.

score 4 · Answer 8 · answered Aug 09 '22 at 17:55

4

go to play console dashboard->App integrity ->app signing you will see SHA-1, SHA256 and MD5 keys

answered Aug 09 '22 at 17:55

user3792893

61
3

score 1 · Answer 9 · edited Aug 09 '22 at 18:02

1

The tried solution: Upgrade your Gradle version

distributionUrl = https \: //services.gradle.org/distributions/gradle-5.4.1-bin.zip in gradle-wrapper.preperties

after that

Navigate to the Gradle tab on the right side of Android Studio
Expand the project name
Expand Tasks
Expand Android
Double click on signingReport

edited Aug 09 '22 at 18:02

TylerH

20,799
66
75
101

answered Dec 27 '20 at 11:45

kksal55

500
7
14

score 0 · Answer 10 · answered Jan 19 '22 at 11:51

If you need it automated, you can extract the value from signingReport gradle task output like this:

function signing_certificate_digest() {
  ./gradlew app:signingReport | \
    awk "/^Variant: $1\$/,/SHA-256|---/" | \
    grep 'SHA-256' | \
    cut -d' ' -f2
}

Which you can use like this in command line:

signing_certificate_digest debug

Also note:

When using Play App Signing, the signature of the binary signed by the upload key certificate will be different than the binary distributed by Google Play.

So this may not be suitable in that case.

score 0 · Answer 11 · answered Aug 09 '22 at 18:01

_{Migrating OP's solution from the question to an answer:}

For Release:

Go to: C:\Program Files\Java\jdk1.7.0_25\bin (or wherever your jdk file is).

Type cmd in address bar in win explorer.

Add: keytool -list -v -keystore "C:\Users\yourUserName\Keystores\android.jks" -alias yourAppName -storepass yourPasswordToKeystore -keypass yourPasswordToRequiredAppKey

Be careful!!!

If you have multiple keys in the keystore, it might not give you the correct matching one to the given app!

Another way of getting the SHA256 for your app:

Either on the Developer Console or Firebase, you can find the related SHA256 key somewhere. I couldn't find it now, but if you keep looking, it is there somewhere.

I just found it on the Google Play Developer Console:

Upload the first version of your app (if you haven't done it yet)

Go to App Releases in Release Management

Click Manage Beta

At the APK version click the "i" info button on the right

It will show you the SHA keys

Android Studio only gives me SHA1, I need SHA256

11 Answers11

For Release:

Another way of getting the SHA256 for your app:

Linked