Facebook key hash does not match any stored key hashes

Question

I'm really having troubles with the Facebook hash key. I generated it in my Eclipse.. proof:

Then I went to https://developers.facebook.com/ and registered a new app.

And finally I've set my hashkey at the settings of Facebook developers:

But no whatter I do I keep getting the same error log: "Key hash B5dWUEYfZJL/...........jyA= does not match any stored key hashes"

Does anybody know what I did wrong or how I can fix this problem? If I used the id and name from the HelloFacebookSample inside my own app everything works. So it HAS to do with the key hash, id or name I've set somewhere most likely..

Thank you, Yenthe

The screen cap where you're showing the key hash settings is the wrong place. "Sample App Settings" is only for key hashes for the sample apps that ship with the SDK (so you can build them locally). You should put the key hashes under the "Android" tab in your app settings. — Ming Li, Nov 30 '13 at 19:38
Yeah I know what you mean and that was my initial fault. I then moved it to the Android tab, but neither that was a succes. I had to manually remove my hash key and generate a new one before it all started working. — Yenthe, Dec 01 '13 at 09:08
delete your app from developers.facebook.com and try this http://stackoverflow.com/questions/4388992/key-hash-for-android-facebook-app/6665263#6665263 — Manmohan Pal, Feb 26 '17 at 06:41

Narender Gusain · Answer 1 · 2015-07-31T06:04:16.453

80

If your login is working without installing facebook app and not working when facebook app is installed due to error "hash key has not match" then do following steps

1 ) Launch your app and try to log in with facebook. A dialog will open and tell you: "the key has not been found in the facebook developer console and also show the hash key.

2 ) Note down that hash key.

3 ) Put it into your facebook developer console where you first generated your api key and remove the hash key with new and save. Now you are done. Anyone that downloads your app, published with earlier used keystore can log into facebook.

edited Jul 31 '15 at 06:04

answered Jul 30 '15 at 13:31

Narender Gusain

1,801
11
13

Thanks. Worked like a charm. – Rajan Maurya Jun 15 '16 at 13:37
1

Nope, didn't work for me. It still works fine without facebook app but if fb app is installed it gives me same error – Ahsan Oct 17 '17 at 20:45
Thanks a lot mate! – Ahsan Oct 18 '17 at 06:17
Release key hash doesn't work for me, but Debug key hash worked ok – Konstantin Konopko Apr 14 '18 at 13:06
Can you please tell me about the concept of keyhashes, what is it actually and on what criteria these gets generated ? – B.shruti Jun 01 '18 at 05:26
should I remove all previous Hash Keys used? – Manny265 Aug 03 '18 at 20:52
Given solution is working fine, for me when I download app from play store and try login then it gives me different hash than generated from release keystore. – nilesh Sep 03 '18 at 06:12
take care with uppercase letters – Juan Angel Mar 08 '19 at 15:26
Just shame on Facebook because of POOR document – Ali Zarei Jun 24 '20 at 06:42

score 45 · Accepted Answer · edited Aug 15 '14 at 14:33

45

After hours of trying I've finally found a solution.

Delete any app on the website of Facebook (developers.facebook.com)
Delete the file debug.keystore under C:\Users\yourUserName\.android
Generate a new key (by running your app again)
Create a new app on developers.facebook.com and add the new hash key
Re-run your app
Succes!

edited Aug 15 '14 at 14:33

Jorgesys

114,263
22
306
247

answered Nov 30 '13 at 18:30

Yenthe

1,997
2
21
44

Thanks! This really works but what if I have a couple of apps registered on the Developers site of Facebook and this issue comes over and over again from time to time? – Yulian Jan 08 '15 at 13:20
@Yulian I'm not sure, that sounds like a very annoying problem.. I'm not sure about this as I only have one app on the Developers site. Sorry! – Yenthe Jan 08 '15 at 13:23
Good to hear that my solution is still working @FernandoP.G.! I'm amazed too that this error is still here after over a year.. – Yenthe Feb 18 '15 at 15:07
94

Now what do we do if we already have thousands of users, just recreating the app isn't exactly a great idea. – Hobbyist May 13 '15 at 12:34
My Review got success. If I create a new app then again I want to submit for review. Is creation new app is mandatory? – Naveen Kumar M Aug 27 '16 at 05:54
Saved my day. Had the same issue. Just changing current FB app with new app solved every thing. Thanks – Rahul Oct 28 '16 at 07:15
I have very similar situation to yours. I didn't remove everything, but created new license, went to my regular FB page - Settings - Apps - Removed the app from the list. Changed hash key in dev account and reinstalled fb app and own app. And now it works...It seems fb "remembers" hash keys. – anna_manzhula Jun 07 '17 at 11:46
7

Deleting apps is not an option, This solved the problem https://github.com/AntonioCuevaUrraco/nativescript-facebook-login/issues/14 – Mustafa Magdy Apr 17 '18 at 03:31
1

Regenerating `debug.keystore` can complicate matters as if you are using firebase with Google Sign-In it will no longer work as a new SHA-1 key will be generated and you would have to update it in your firebase app page – Kewal Shah Jun 08 '18 at 09:44
What about apps that are already on the store and that have users already using facebook? You can't just delete the app. – skydev Oct 31 '18 at 14:07
I have the same error but when I didn't set any password in "Enter keystore password:" (Leave it blank and just hit Enter) then it works. It gives some warning but it works – Erfan Jazeb Nikoo Dec 02 '18 at 12:39
I have permissions on the app, it would be a a long process to get things in order again if I remove it – Tushar Gogna Mar 18 '19 at 07:55

Bashar Ali Labadi · Answer 3 · 2014-12-04T09:26:54.520

I faced the same issue while development and needed to get the hash key to test sharing on facebook, and while solving this I went through couple of issues

1- the command facebook provide to get the hash key by using openSSL command didn't give me the right hash that I got by extracting the signature from Package info with code. getting the hash by the second way was correct.

2- For some reason, In the documentation they tell you to go to developer settings and add the hash key for 'Sample App' there, I thought every hashkey for a developer should be there, and that was my mistake, every app has it's own hash keys field to add to, go to your app/settings/android.

enter image description here

well that was it.. and for the records I used openssl-0.9.8k_X64 on a Windows 7 x64 bit and it just generates a wrong hash I don't know why

I used this code to get the hash:

private void printKeyHash() {
    // Add code to print out the key hash
    try {
        PackageInfo info = getPackageManager().getPackageInfo("YOUR PACKAGE NAME", 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 (NameNotFoundException e) {
        Log.e("KeyHash:", e.toString());
    } catch (NoSuchAlgorithmException e) {
        Log.e("KeyHash:", e.toString());
    }
}

but be careful that this may not also print in logs the correct keyhash, at least on my device and machine, when I debug it, in a watch it shows the correct hash just before printing the logs, but in logs it shows another hash and the first one was the correct one.

anyway you can also use a command or eclipse to view the SHA hexadecimal sequence for your key and convert it to base 64 online, there are websites that may help http://tomeko.net/online_tools/hex_to_base64.php?lang=en

Good luck

this one did it for me! thanks buddy! i added that code into my oncreate function for my mainactivity and check the result in my logcat console, filtered by "KeyHash" and got that key pasted in my app dashboard, it worked perfectly ! — Fo Nko, May 27 '18 at 23:11
i sent my app to a friend, and he has the same issue... it's wokring for me but he can't log ! why is that? — Fo Nko, May 28 '18 at 00:10

score 36 · Answer 4 · answered Jul 05 '16 at 00:54

36

I encountered a similar problem. The solution is surprisingly simple.

The error message looks like this:

07-05 ...... Invalid key hash. The key hash sL1***************VY= does not match any stored key hashes. Configure your app key hashes at http://developers.facebook.com/apps/150*******778
07-05 ......     at com.facebook.login.LoginManager.onActivityResult(LoginManager.java:191)

Simply log into https://developers.facebook.com , select the "Settings" tab, and add the key hash "sL1***************VY=" to the list of saved Key hashes in the Android panel.

answered Jul 05 '16 at 00:54

Darsen Lu

573
6
10

2

This is the best answer. – abelabbesnabi Mar 15 '17 at 03:21
Its a perfect answer – Sushin Pv Jan 25 '18 at 10:01
and, when asked for debug key password, which you never set, type `android` and thank me later :) – touhid udoy Dec 10 '18 at 08:06
5

exception doesn't return the key hash anymore – Tamim Attafi Feb 24 '19 at 16:41
even this didn't work for me, I uninstalled facebook app and it worked as mentioned in another answer – jayasurya_j Mar 05 '19 at 16:53

Moustafa EL-Saghier · Answer 5 · 2021-05-29T12:01:32.150

DATE UPDATED EVERY TIME I GOT UPVOTE AS I KNOW IT STILL VALID

DATE: 29/05/2021 (29th of May2021)

This is how I solved this problem

I have got the SHA1 from signingReport

(found in gradle-->tasks/android/signingReport)

Copy the SHA1 value to your clipboard

like this XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX

Facebook sdk requires it to be in base64 hash key so we open 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 " ********************= "

open https://developers.facebook.com/
select your project in the setting tab, basic/Key Hashes add the generated key.
don't forget to save changes.

Kewal Shah · Answer 6 · 2020-05-26T17:13:27.710

34

This is a case that could have possibly occurred and what solved my error:

In the https://developers.facebook.com/quickstarts after you run

OSX/Linux:

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64

Windows:

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

When Enter keystore password: is asked you may have accidentally typed a wrong password, the default password is "android". Typing any other password will give you a different/wrong hash key. Paste the correct hash key in the Key Hashes field on your app page

This solved my problem, hope this helps whoever made this particular error that I made

edited May 26 '20 at 17:13

answered Jun 08 '18 at 08:34

Kewal Shah

691
11
24

Is it possible to change the default password? if so how\where? – Coder123 Jan 02 '19 at 16:02
@Coder123 just create your own `debugAlt.jks` in another directory with different password and key and put it in your `signingConfigs { debug { storeFile file(new File('../debugKey.jks')) storePassword "Qwerty123" keyAlias "debug" keyPassword "Qwerty123" } }` – Variag Jan 10 '19 at 21:52
you mean we should compulsorily use "android" as password? where is it written? – user1090751 Jan 23 '20 at 15:00
@user1090751 click on the "android" link in my answer for more details. You can create your own password as pointed out in the previous comment – Kewal Shah Jan 24 '20 at 10:12
Thank you for this password! That solved it for me! – ljubiccica Mar 20 '20 at 16:12

score 18 · Answer 7 · edited Jun 20 '20 at 09:12

18

---2019----- This is how i solved this problem

in android studio in right panel Gradle>App>android>signingReport copy SHA1
and open 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 the facebook app.

edited Jun 20 '20 at 09:12

Community

1
1

answered Aug 07 '19 at 08:57

Govan

940
1
10
11

Thanks, This solved my problem. Why keytool version not working it is interesting – Nijat Aliyev Nov 30 '20 at 19:50

score 17 · Answer 8 · answered Jul 23 '14 at 08:14

17

Adding SHA1 keys from Eclipse/keytool helped me only when creating the app on FB, then after rebuilding I would always get the OP error.

What solved my issue was adding the key in the error message to the Facebook dashboard settings.

answered Jul 23 '14 at 08:14

Peter File

975
9
22

3

For debug key alright, but how can I know about error message from app installed via apk? – kostyabakay Aug 19 '16 at 08:33

score 9 · Answer 9 · edited Apr 26 '16 at 02:12

9

Check your Key hash value.
Uninstall the Facebook application from your phone.
Then try again using SDK.

This solved my problem.

edited Apr 26 '16 at 02:12

Pang

8,605
144
77
113

answered Dec 29 '15 at 06:37

Rezaul Karim

1,126
17
25

2

Uninstalling FB app solved the problem!! Thank you :) – nithinreddy Jun 17 '18 at 09:20
@Rezaul Karim it works, but what if i want to make it work without installing fb app? – divaPrajapati09 Feb 11 '19 at 08:49

Thamim · Answer 10 · 2020-11-02T10:04:33.800

While generating release Hash key, Note this

For Windows

When generating the hash key for production you need to use openssl-0.9.8e_X64.zip on windows, you cannot use openssl-0.9.8k_X64.zip

The versions produce different hash keys, for some reason 9.8k does not work correctly... 9.8e does.

OR

Use this below flow

This is how i solved this problem Download your APK to your PC in java jdk\bin folder in my case C:\Program Files\Java\jdk1.7.0_121\bin go to java jdk\bin folder and run cmd then copy the following command in your cmd

keytool -list -printcert -jarfile yourapkname.apk

Copy the SHA1 value to your clip board like this CD:A1:EA:A3:5C:5C:68:FB:FA:0A:6B:E5:5A:72:64:DD:26:8D:44:84 and open http://tomeko.net/online_tools/hex_to_base64.php to convert your SHA1 value to base64.

For MAC

Step 1:

Generate SHA1 key by using below command
keytool -list -v -keystore Keystore path
Enter Keystore password.
Copy SHA1 Key.

Step 2:
Open this link - http://tomeko.net/online_tools/hex_to_base64.php
Paste the SHA1 Key in Hex String
Click convert button
Get the Release Keyhash in Output value

this solved my problem `keytool -list -printcert -jarfile yourapkname.apk` :) — Hawk, Jun 03 '20 at 23:47

score 9 · Answer 11 · answered Oct 10 '19 at 14:53

9

Follow these steps in order to generate the correct key hashes.

Open your project in android studio and run the project.
Click on Gradle menu.
Select your app and expand task tree.
Double click on android -> signingReport and see the magic
Result after clicking above tab
Copy the SHA1 key and browse SHA1 key to key hash
After converting the SHA1 key to key hash copy the new key hash and paste it in facebook console. This will work like charm.

answered Oct 10 '19 at 14:53

Pratap Sharma

1,645
1
13
23

1

Nice easy solution, just make sure you copy the sha1 from the correct Variant, in my case it was release. – Francis Malloch Apr 12 '20 at 06:50

score 7 · Answer 12 · answered Jan 29 '15 at 00:16

I have had this Problem for two months now. My key hashes have been pyling up to 9. Today i finally found the simple solution:

STEP 1:

Install the facebook sdk you downloaded from the facebook developer page on your phone. Don´t install the normal facebook app. Make sure you can log into facebook. Then log out.

STEP 2:

Export your app with your final release key as an apk, like you would when uploading it to the playstore.

STEP 3:

Put the Apk file on your phone via usb cable or usb stick.

STEP 4:

Install your app, using a file manager: For example https://play.google.com/store/apps/details?id=com.rhmsoft.fm

STEP 5:

Launch your app and try to log in with facebook. A dialog will open and tell you: "the key has not been found in the facebook developer console

STEP 6:

Write down the key.

STEP 7:

Put it into your facebook developer console and save. Now you are done. Anyone that downloads your app, published with earlier used keystore can log into facebook.

Enjoy

am fallowing your tips pasted that facebook-universalsignin.apk in to mobile and istalled that.and then my app install and runned in that situation also facebook popup openned for login no other dialog box coming please help me — Harsha, Nov 08 '16 at 13:22
Did you install the facebook sdk form the developer page and uninstall the normal facebook app from the playstore? — Sakramento, Jan 06 '17 at 14:51

score 6 · Answer 13 · answered Nov 10 '16 at 08:23

It is looks crazy but it work

Really issue because of you privite facebook account got this app and hash key of this account does't comparable

But you musn't to faced this error with real user. But I am not sure

Eventually follow next step :

Go to your private facebook account which you try to log in
Then click More in app dir

Click Settings

And then click cross

And now you can login with facebook. But next time if you log out and than will try log in again you faced with the same issue...

It is also weird...

But I don't bellieve that facebook don't know about this ...

score 6 · Answer 14 · answered May 17 '20 at 10:22

This worked for me

Go to Google Play Console
Select Release Management
Choose App Signing
Convert App-Signing Certificate SHA-1 to Base64 (this will be different than your current upload certificate) using this tool: http://tomeko.net/online_tools/hex_to_base64.php?lang=en
Enter Base64 converted SHA-1 into your Facebook Developer dashboard settings and try again.

score 5 · Answer 15 · edited Jun 20 '20 at 09:12

5

I am also getting the same issue when user try to Login with Facebook.

Not Working: Facebook App is Installed in Device.

Working: Facebook app is not installed

So, following Code is resolved the issue event the Facebook app is installed in device.

LoginManager.getInstance().setLoginBehavior(LoginBehavior.WEB_ONLY); //This Line Solved Issue
LoginManager.getInstance().logInWithReadPermissions(context, Arrays.asList("public_profile", "email"));

edited Jun 20 '20 at 09:12

Community

1
1

answered Dec 13 '19 at 04:29

Ketan Ramani

3,300
24
36

2

saved my hours ..!! – Himani May 07 '21 at 09:39

score 4 · Answer 16 · answered Jul 01 '19 at 16:01

What I found was that my SHA-1 that was used to sign the app to be uploaded to the Google Playstore was not correct. I realized that my app was being signed by the Google Play Store with a different token. I followed these steps:

Go to Google Play Console
Click Release Management
Click App Signing
Convert App-Signing Certificate SHA-1 to Base64 (this will be different than your current upload certificate)
Enter Base64 converted SHA-1 into my Facebook Developer dashboard settings

I am now able to log into my app when the Facebook is downloaded on and Android device.

score 3 · Answer 17 · answered Apr 18 '15 at 13:32

Using Debug key store including android's debug.keystore present in .android folder was generating a strange problem; the log-in using facebook login button on android app would happen perfectly as desired for the first time. But when ever I Logged out and tried logging in, it would throw up an error saying: This app has no android key hashes configured. Please go to http:// ....

Creating a Keystore using keytool command(keytool -genkey -v -keystore my-release-key.keystore -alias alias_name -keyalg RSA -sigalg SHA1withRSA -keysize 2048 -validity 10000) and putting this keystore in my projects topmost parent folder and making a following entry in projects build.gradle file solved the issue:

 signingConfigs {
        release {
            storeFile file("my-release-key.keystore")
            storePassword "passpass"
            keyAlias "alias_name"
            keyPassword "passpass"
        }    }

Please note that you always use the following method inside onCreate() of your android activity to get the key hash value(to register in developer.facebook.com site of your app) instead of using command line to generate hash value as command line in some cased may out put a wrong key hash:

    public  void showHashKey(Context context) {
        try {
            PackageInfo info = context.getPackageManager().getPackageInfo("com.superreceptionist",
                    PackageManager.GET_SIGNATURES);
            for (android.content.pm.Signature signature : info.signatures) {
                MessageDigest md = MessageDigest.getInstance("SHA");
                md.update(signature.toByteArray());

                 String sign=Base64.encodeToString(md.digest(), Base64.DEFAULT);
                Log.e("KeyHash:", sign);
                //  Toast.makeText(getApplicationContext(),sign,     Toast.LENGTH_LONG).show();
            }
            Log.d("KeyHash:", "****------------***");
        } catch (PackageManager.NameNotFoundException e) {
e.printStackTrace();
        } catch (NoSuchAlgorithmException e) {
e.printStackTrace();
        }
    }

showHashKey function works like a charm getting the key, tnx — dianakarenms, May 31 '16 at 00:58

Leo Nguyen · Answer 18 · 2018-05-21T09:03:21.760

3

I got the same problem. I found that I used wrong hashkey. keytool printed wrong hashkey because I run command with wrong alias.
Please check your command again.It will resolve your issue

keytool -exportcert -alias "test fb sdk" -storepass android -keypass android -keystore "C:\keystore.keystore" | openssl sha1 -binary | openssl base64

edited May 21 '18 at 09:03

answered May 08 '15 at 04:02

Leo Nguyen

604
1
9
23

score 1 · Answer 19 · answered Jul 12 '17 at 09:39

I got simular problem. After signing and publishing my app to the google PlayStore it seems the Hash has changed. I added the new Hash (as mentioned) in the Facebook messaged to the Key Hashes in my app on developers.facebook.com/app//settings. Now it works again.

score 1 · Answer 20 · answered May 17 '19 at 18:15

1

You are may be using wrong password the default password for debug keystore is android

answered May 17 '19 at 18:15

Tausif Ul Rahman

116
5

score 1 · Answer 21 · answered Jul 18 '19 at 09:57

My problem is possibly due to the hash got wrongly generated by the openssl itself, if anyone is facing similar problem using the method provided by the facebook android guide itself.

One way to deal with this is :

Get your sha1 using this tool :

keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v

convert it to base64 using this tool

http://tomeko.net/online_tools/hex_to_base64.php

credit :

https://github.com/facebook/react-native-fbsdk/issues/424#issuecomment-469047955

yes, same for me. i did it right but openssl did something and it was not correct. It took 6hours of my time. — touhid udoy, Sep 14 '19 at 18:21

score 0 · Answer 22 · answered Feb 05 '20 at 07:10

@Ketan Ramani answer helped me but in my case, I was not using the LoginManager instead I was registering a callback on an image if you are using registerCallback on any image by making it a login button use below code

 loginButton.setLoginBehavior(LoginBehavior.WEB_ONLY);

score 0 · Answer 23 · answered Feb 16 '20 at 17:09

0

I have tried everything on this page but no success, until i took a break, then when I continue working on this, without changing anything, it suddenly works. Maybe (just maybe) facebook needs times to register the key

answered Feb 16 '20 at 17:09

Irfandi D. Vendy

594
9
18

score 0 · Answer 24 · answered Jun 20 '20 at 08:57

0

Here is Nice Solution for macOs And It works for me :

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64

Here key store password should be android . Thanks

answered Jun 20 '20 at 08:57

Mir Mahfuz

221
2
7

score 0 · Answer 25 · answered Aug 19 '20 at 13:55

In the right side of Android Studio go to Gradle -> Tasks -> android -> signingReport and run it. Copy the SHA-1 key and transform it into base64 using this, and then add the converted base64 hash to your app in the Facebook Developer Console. If you want to use a release hash run this in the command line:keytool -exportcert -alias YOUR_KEYSTORE_ALIAS -keystore YOUR_KEYSTORE | openssl sha1 -binary | openssl base64 Where YOUR_KEYSTORE is the path to the .keystore or .jks that you used as signinConfig for your release variant and YOUR_KEYSTORE_ALIAS is the alias which you gave when you created the keystore. If you do not remember the alias you can run keytool -v -list -keystore YOUR_KEYSTORE and see all the info about the keystore

score 0 · Answer 26 · answered Sep 27 '20 at 12:40

On Debug

Copy Paste This code inside OnCreate method

       try {
            PackageInfo info = getPackageManager().getPackageInfo(
                    getApplication().getPackageName(),
                    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) {
            Log.d("KeyHash e1",e.getLocalizedMessage() +"");
        } catch (NoSuchAlgorithmException e) {
            Log.d("KeyHash e2", e.getLocalizedMessage() +"");
        }

Open Logcat and Filter/find 'D/KeyHash:'

D/KeyHash: D5uFR+65hafzotdih/dOfp14FpE=

Then Open https://developers.facebook.com/ and Open YourApp/Setting/Basic
Scroll down to Android Section Then Paste the Key Hashes and Save

score 0 · Answer 27 · answered Nov 30 '20 at 18:32

0

Just run command adb logcat | grep hash and look for something like Key hash ABCDEFGH1234= does not match any stored key. Now save this hash on your fb developer console.

answered Nov 30 '20 at 18:32

Dinesh Verma

406
2
8

score 0 · Answer 28 · answered Apr 24 '21 at 06:08

I have same problem when I so facebook integration, and I solved this error by this steps:

open android folder(File/open/yourFlutterProject/android) in your flutter project
now you can see gradle field in right-side top penal -------
do this steps(gradle/android/app/tasks/android/signingReport) and click it.
now you can see your project SHA-1 key, note it.
now open this site(Site Link) and convert SHA-1 to keyhash and you get your keyhash value, note it.
not update/change this keyhash with currunt keyhash in your developer.facebook console
now its run perfect.

score -2 · Answer 29 · answered Jan 10 '17 at 06:26

-2

Check your google-services.json . May be it is different one. Download your latest google-services.json and then run the app. Hope it helps.

answered Jan 10 '17 at 06:26

Shubham Gupta

95
1
4

Facebook key hash does not match any stored key hashes

29 Answers29

Linked