Android app Key Hash doesn't match any stored key hashes

P

14

33

I have an application on production on Play Store which uses a login with the Facebook SDK. When I debug the application from Eclipse there is no problem, but when its on production it gives me the following error after Facebook asks me for the permissions. I have added on my app page on developers.facebook.com the key hash generated with keytool using this command:

keytool -exportcert -alias diego -keystore "C:\Users\Diego\Desktop\CeluChat.KeyStore" | "C:\openssl\bin\openssl.exe" sha1 -binary | "C:\openssl\bin\openssl.exe" base64

CeluChat.KeyStore is the keystore I used when I exported the signed application, and when keytool promts me for the password, I entered the same when exported.

But the error that gives me on production (downloaded from Play Store) is:

10-20 22:21:10.752: W/fb4a(:):BlueServiceQueue(5872): com.facebook.http.protocol.ApiException: Key hash VQ3XhZb5_tBH9oGe2WW32DDdNS0 does not match any stored key hashes.

The Key Hash that is on the exception is different from the key hash generated with keytool. Anyway I added the Key Hash on Facebook, but it is still not working.

Parliamentary answered 21/10, 2013 at 1:39 Comment(4)

There are today a global problem in Facebook, check it later – Haiduk 21/10, 2013 at 13:58

When you submit an apk for the play store, usually that's using a different keystore than when you're in development, which would give you a different key hash. You need to put both key hashes into your settings. Are you sure that the value given in the error doesn't work either? Can you post a screen shot of your app settings? – Correct 21/10, 2013 at 14:2

The key hash that I was generating with keytool was with the relase key, not with the debug, so the problem was not that. Thanks anyway – Parliamentary 21/10, 2013 at 16:19

If you are copying the key hash from log and using it, note that in the log it does not print with a = in the end, you must suffix a = to what is printed in the log and then use it in the Facebook key hash. – Craver 25/6, 2015 at 11:33

S

29

Facebook some how replaces +,- and / with _

So just try replacing _ with +, - and / and add that hash-key.

Hopefully it should work.

Superfecundation answered 21/10, 2013 at 16:1 Comment(9)

To find the EXACT value that you need, run this command (it will require your keystore password): keytool -exportcert -alias <RELEASE_KEY_ALIAS> -keystore <RELEASE_KEY_PATH> | openssl sha1 -binary | openssl base64 – Hepzi 12/12, 2013 at 8:11

the hash key should contain '='? – Cloak 12/12, 2013 at 12:15

I have none of these symbols in my key, so nothing to replace there. = is at the end, it´s exactly the same key as the log says, but nothing is working – Vaishnava 14/1, 2014 at 21:57

I need to replace "_" instead of "/" on my hasy key. But im little bit confusing where should i replace. Im using following key on my facebook app. gtKHgB36QgyFMUrCFDtAFdKrc/8= – Balinese 26/2, 2014 at 15:7

This is a poor method as it's just hit and trial, it may vary. Adding Trailing '=' also doesn't seem to work now. – Urbina 13/5, 2014 at 9:10

same as @Youngjae, I just added '=' at the end. This is insane. – Gaslit 7/8, 2014 at 17:1

I had to get over to developers.facebook.com, select the app and then "settings" on the left. Scroll down to Android => add the key here, for some reason it would only show the release key hash there, adding the debug key hash there fixed it for me. – Sicilia 26/2, 2015 at 15:52

Just for heads up, when using Win PowerShell then the hash will have a different value and no '=' in the end which will give you the trailing '=' error. I did the same commands with original cmd and it worked. Don't know why PowerShell messes it up. – Oboe 24/9, 2016 at 11:47

I am also getting Hashkey error for Facebook login.. but it is working fine in few apps and not working in few apps.. i am totally confuse what to do.. I have change the hash key many times then also I am facing this problem. My App is publish on playstore that time I am getting this error., When I directly install from androidStudio it is working fine..please Help.. – Schmuck 8/4, 2019 at 12:32

M

29

I used this to show the key when I ran my app. In my case, I was getting the incorrect key hash from the keytool command. Notice that if you enter the wrong password(purposely), instead of receiving an error an incorrect key is generated. Use this to get the correct hash and see if it matches the one the in the error log

try {
        PackageInfo info =     getPackageManager().getPackageInfo("com.package.mypackage",     PackageManager.GET_SIGNATURES);
        for (Signature signature : info.signatures) {
            MessageDigest md = MessageDigest.getInstance("SHA");
            md.update(signature.toByteArray());
            String sign=Base64.encodeToString(md.digest(), Base64.DEFAULT);
            Log.e("MY KEY HASH:", sign);
            Toast.makeText(getApplicationContext(),sign,     Toast.LENGTH_LONG).show();
        }
} catch (NameNotFoundException e) {
} catch (NoSuchAlgorithmException e) {
}

Also, if for some reason the above method does not work. Try using this APK to generate the correct key hash. Remember that you have to sign it with whatever certificate you are trying to retrieve(debug or release). Install it on your testing device, and run it.

http://www.easyfacebookandroidsdk.com/download/keyhash.zip

Migraine answered 21/10, 2013 at 2:38 Comment(4)

I used that code and discovered that the key hash was the same that facebook gives on the exception, but replacing "_" with "/" and adding a "=" on the end. Thanks – Parliamentary 21/10, 2013 at 16:17

It didn't replace anything for me but missed the "=" at the end too. – Glyptodont 28/6, 2015 at 18:46

@DiegoSuárez how to replace "_" with "/" I have just changed it but it is not getting saved there as Keyhash. Please let me know the way for that. – Defense 2/6, 2016 at 8:46

This work for me. The command with keytool and openssl in the official doc return the difference hash. :(( – Tuning 2/9, 2021 at 13:51