The Key Hash Does not match any store key hashes.

[i-suraj]

I tried to generate hash by using
>keytool -exportcert -alias payoja -keystore "C:\Users\Epsum Labs\Desktop\PAYOJA\android\app\payoja.keystore" | "C:\Users\Epsum Labs\Desktop\openssl\bin\openssl" sha1 -binary | "C:\Users\Epsum Labs\Desktop\openssl\bin\openssl" base64

I am unable to login neither in debug nor in release mode.

[humarkx]

I have the same problem, without the app installed, it works, when the facebook app is installed, I get the invalid key hash, however, the hash that gives on the error, is on facebook app.

Help plz

[sergiulucaci]

Make sure you get the hash of the signed key used for generated APK.

MacOS:

keytool -exportcert -alias <RELEASE_KEY_ALIAS> -keystore <RELEASE_KEY_PATH> | openssl sha1 -binary | openssl base64

Real example, assuming that keystore is placed under android/app:

keytool -exportcert -alias my-key-alias -keystore android/app/my-release-key.keystore | openssl sha1 -binary | openssl base64

This will generate a hash key that must be placed into app's profile:

1. Go to https://developers.facebook.com/apps/YOUR_APP_ID/settings/basic/
2. Scroll down to Android Key Hashes
3. Place the key there

Source

[i-suraj]

any solution for this???

[drpshtiwan]

Here is the same, anyone has any solution??

[duarte-evocorp]

I have the same problem

[CapitanRedBeard]

For me it was redirecting to the FB app and it was displaying a hash that I never generated. I copied that hash into the FB console and it seemed to work after that. Not quite sure why.

[Ovi]

This worked for me.

Copy the APK to your PC in Program Files\java\jdkX.X.X_XXX\bin folder

In my case it's C:\Program Files\Java\jdk1.8.0_191\bin

Open CMD in this directory and type the following

keytool -list -printcert -jarfile YOUR_APK_NAME.apk

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

[nuclearWinters]

I used the openssl version "openssl-0.9.8e_X64.zip" in windows, the others generate false hashes

[masierraf]

Anyone has any solution?

[ramanaptr]

• I've been solved this issue using java/kotlin code here

Kotlin:

    fun createKeyHash(activity: Activity, yourPackage: String) {
        val info = activity.packageManager.getPackageInfo(yourPackage, PackageManager.GET_SIGNATURES)
        for (signature in info.signatures) {
            val md = MessageDigest.getInstance("SHA")
            md.update(signature.toByteArray())
            Log.d("KeyHash:", Base64.encodeToString(md.digest(), Base64.DEFAULT))
        }
    }

Java:

    public static void createKeyHash(Activity activity, String yourPackage) {
        try {
            PackageInfo info = activity.getPackageManager().getPackageInfo(yourPackage, PackageManager.GET_SIGNATURES);
            for (Signature signature : info.signatures) {
                MessageDigest md = MessageDigest.getInstance("SHA");
                md.update(signature.toByteArray());
                Log.d("KeyHash:", Base64.encodeToString(md.digest(), Base64.DEFAULT));
            }
        } catch (PackageManager.NameNotFoundException e) {
            e.printStackTrace();
        } catch (NoSuchAlgorithmException e) {
            e.printStackTrace();
        }
    }

and call your function like this

createKeyHash(this, "com.ramana.myapp")

Note: "com.ramana.myapp" it is my package path/name and to see your keyhash please type search the debug on logcat with message 'KeyHash'.
Base64 must be import android.util.Base64 dont import java.util.*

[UzairAhmedSiddiqui]

Solved this for myself, I carefully added the correct hash of my release key but my app keep complaining about key hash does not match any store key hashes and showed a hash which was different from my release key hash.
After going nuts over where this new hash comes from I finally figured out that google play probably also signs the apk when you upload it. so after publishing if you go to google play console you will see find versions of the apk, one signed by your release key and another derived apk probably signed by google.

You have to download the derived apk and get the SHA1 hash using
keytool -list -printcert -jarfile YOUR_APK.apk
the output will be in Hex so you'll have to convert it into base64, and it will be the same hash that the app complains about after being published to store.

I don't know why this isn't mentioned in facebook dev console and their docs.

[tuononh]

Check if your "App Signing by Google Play" is enabled. Then copy SHA1 from there and go to http://tomeko.net/online_tools/hex_to_base64.php to get the key hash.

[jagmel]

Recently found this Hasher App which helps in extracting keyhash from sha1 (from google play store console) and vice-versa

[Seerat-Ahmed]

Solved this for myself, I carefully added the correct hash of my release key but my app keep complaining about key hash does not match any store key hashes and showed a hash which was different from my release key hash.
After going nuts over where this new hash comes from I finally figured out that google play probably also signs the apk when you upload it. so after publishing if you go to google play console you will see find versions of the apk, one signed by your release key and another derived apk probably signed by google.

You have to download the derived apk and get the SHA1 hash using
keytool -list -printcert -jarfile YOUR_APK.apk
the output will be in Hex so you'll have to convert it into base64, and it will be the same hash that the app complains about after being published to store.

I don't know why this isn't mentioned in facebook dev console and their docs.

This solved my problem :)

[MayarAhmed]

@UzairAhmedSiddiqui unfortunately i followed these steps but didn't work with me

Did you figure any other solution??

[UzairAhmedSiddiqui]

@UzairAhmedSiddiqui unfortunately i followed these steps but didn't work with me

Did you figure any other solution??

@MayarAhmed I'm afraid not, but if the error is the same then it should work, the problem simply is that the hash of the signed apk and the one set on facebook dev console do not match.
If you're also signing the apk yourself then you can try disabling app signing by google play and use the hash of your own certificate.

[MayarAhmed]

this step solved it for me

Copy the File debug.keystore from .android folder in my case (C:\Users\SYSTEM.android) and paste into JDK bin Folder in my case (C:\Program Files\Java\jdk1.6.0_05\bin)

and then excute cmd

keytool -exportcert -alias androiddebugkey -keystore %HOMEPATH%.android\debug.keystore | openssl sha1 -binary | openssl base64

which gives me the same hash code in the error and then it solved

[BDominik]

This worked for me.

Copy the APK to your PC in Program Files\java\jdkX.X.X_XXX\bin folder

In my case it's C:\Program Files\Java\jdk1.8.0_191\bin

Open CMD in this directory and type the following

keytool -list -printcert -jarfile YOUR_APK_NAME.apk

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

Thank you this is helped me.

[milkmanjr]

This fixed it for me

expo/expo#2079

Specifically expo/expo#2079 (comment)

[nguyen95]

We can get hash from Android studio: CLick Gradle --> double clicks signingReport --> get SHA1 --> convert to hash

[ChinGyi2019]

#424 (comment)
here is the answer above Explain!! thanks

[amitbravo]

This worked for me.

Copy the APK to your PC in Program Files\java\jdkX.X.X_XXX\bin folder

In my case it's C:\Program Files\Java\jdk1.8.0_191\bin

Open CMD in this directory and type the following

keytool -list -printcert -jarfile YOUR_APK_NAME.apk

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

what possible location can be for OSX ?

[kenpham4real]

This worked for me.

Copy the APK to your PC in Program Files\java\jdkX.X.X_XXX\bin folder

In my case it's C:\Program Files\Java\jdk1.8.0_191\bin

Open CMD in this directory and type the following

keytool -list -printcert -jarfile YOUR_APK_NAME.apk

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

I met the same issue while I did generate a SHA1 key before. I solved it now thanks to the link you provide. Thank you very much !

[trOnk12]

Somehow when I am running it in windows powershell the generated code has the wrong format but when I run it in cmd the format is valid, hopefully it helps someone.

[ghasemikasra39]

any solution ?

[Hansel03]

We can get hash from Android studio: CLick Gradle --> double clicks signingReport --> get SHA1 --> convert to hash

This worked for me.

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

[PirunSeng]

Hi there, same issue here. But first, I wonder why the complaint invalid key hash is different from the one I have. And second, where I can get the apk file? During development, is it required that we need to register the app with Google Play?
PS: I am using Windows OS.

[SaravananRath]

This worked for me.

Copy the APK to your PC in Program Files\java\jdkX.X.X_XXX\bin folder

In my case it's C:\Program Files\Java\jdk1.8.0_191\bin

Open CMD in this directory and type the following

keytool -list -printcert -jarfile YOUR_APK_NAME.apk

Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52

Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

Use the above method to generate the key.(Just create a debug apk and run the command pointing to it.)
After spending couple of hours on this. I found out.
No point of adding keyhash here(as per documentation) - https://developers.facebook.com/settings/developer/sample-app/

Add the Key Hash Here - https://developers.facebook.com/docs/facebook-login/android/v2.2

1. Select your app name
2. Add keyhash in step 6.

[PirunSeng]

Hi there, same issue here. But first, I wonder why the complaint invalid key hash is different from the one I have. And second, where I can get the apk file? During development, is it required that we need to register the app with Google Play?
PS: I am using Windows OS.

Just solved my issue by pointing to debug keystore in the project itself "PATH_TO_YOUR_PROJECT/android/app/debug.keystore"

[brianasu-notdoppler]

If you use Google's new android upload key method then your apk gets re-signed after it uploads. The keystore you use to upload is not the actual keystore google signs it with.

You have to go into your Google play release page and download the resigned apk before doing the above steps by OVI. They called it derived APK.

[parnekov]

We can get hash from Android studio: CLick Gradle --> double clicks signingReport --> get SHA1 --> convert to hash

This worked for me.
Copy the SHA1 value to your clipboard It will be something like this: 79:D0:E6:80:4E:28:1E:D1:88:28:CB:D7:E6:BE:2E:0C:FB:24:98:52
Then go to http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.
This is what Facebook requires get the generated hash " ********************= " and copy the key hash to your Facebook developers app settings.

This works on Mac. Thank you!!!

[Blossom-Solutions]

Hi there, same issue here. But first, I wonder why the complaint invalid key hash is different from the one I have. And second, where I can get the apk file? During development, is it required that we need to register the app with Google Play?
PS: I am using Windows OS.

Just solved my issue by pointing to debug keystore in the project itself "PATH_TO_YOUR_PROJECT/android/app/debug.keystore"

You are a saviour mate, this worked for me. Kudos!

[d0uguit0s]

Olá, mesmo problema aqui. Mas primeiro, eu me pergunto por que o hash da chave inválida da reclamação é diferente do que eu tenho. E em segundo lugar, onde posso obter o arquivo apk? Durante o desenvolvimento, é necessário registrar o aplicativo no Google Play?
PS: Estou usando o sistema operacional Windows.

Acabei de resolver meu problema apontando para debug keystore no próprio projeto "PATH_TO_YOUR_PROJECT / android / app / debug.keystore"

eu quero te agradecer mil milhões <3