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
Solution 3
After hours of trying I've finally found a solution.
https://stackoverflow.com/questions/20301025
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianC:\Users\yourUserName\.androidOTHER TIPS
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.
DATE UPDATED EVERY TIME I GOT UPVOTE AS I KNOW IT IS STILL VALID
DATE: 1/07/2022 (1st of July 2022)
This is how I solved this problem
signingReport(found in gradle-->app/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.phpto 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.
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
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.
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
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.
---2019----- This is how i solved this problem
Gradle>App>android>signingReport copy SHA1This is what Facebook requires get the generated hash " ********************= " and copy the key hash to the facebook app.
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.
Follow these steps in order to generate the correct key hashes.
This solved my problem.
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 worked for me
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
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 :
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 ...
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"));
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:
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.
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();
}
}
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
For Windows Only:
At first I used "openssl-0.9.8k_X64.zip" for generate hash of key. This problem appears.
Then I used the openssl version "openssl-0.9.8e_X64.zip" in windows. Then the problem solved.
https://code.google.com/archive/p/openssl-for-windows/downloads
I think most of us having same problem.
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
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.
For signing the developer build, you will use the keystore and key generated by Android Studio. You can retrieve this with the following command:
keytool -exportcert -storepass android -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64
Thanks
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.
You are may be using wrong password the default password for debug keystore is android
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 :
keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v
http://tomeko.net/online_tools/hex_to_base64.php
credit :
https://github.com/facebook/react-native-fbsdk/issues/424#issuecomment-469047955
@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);
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
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
I have same problem when I so facebook integration, and I solved this error by this steps:
What worked in my case:
