I am finishing an app that uses the Android Facebook SDK, in order to login with Facebook. My app must be configured with the proper generated key hash, that must exist on my computer and that must also be set into my Facebook developper console.
When I print the current key hash from my Android app, using the piece of code found on other similary stackoverflow posts, it logs me an old keyhash that I used by the past into my Facebook Developper console. It may be the debug keyhash.
Now I try to generate a release keyhash with the keytool command.
As I am working on a Mac :
keytool -exportcert -alias MyReleaseKey -keystore ~/.android/myreleasekey.keystore | openssl sha1 -binary | openssl base64
I tried almost everything, but this command never asks me for a password, and the file is never generated. Some people says that if it isn't asking for a password, then the entered path may be invalid.
So, I tried all paths, and all the things I could find on internet, such as deleting the ~/.android/debug.keystore which is generated by Android studio. Nothing works...
Why can't I generate my release keyhash ?
Does it have to be stored into the ~/.android/ folder ?
I know that when generating the debug keyhash, we must enter the "android" password as the keystore password. Can I enter the password I want for the release keystore ?
and the file is never generated.
Why do you expect a file to be generated? That command is simply supposed to output a string you then paste into the Facebook dev console.
How do you generate your release APK? Look into app/build.gradle or go to Build -> Generate Signed APK inside of Android Studio and look for the path of your keystore file (it could end with .keystore or .jks).
For now, simplify the command to generate the APK until you're certain you've found the path. Using only
keytool -exportcert -alias MyReleaseKey -keystore ~/.android/myreleasekey.keystore
won't mask any errors, and tell you exactly what's wrong.
I am using following command to generate my has key.
keytool -exportcert -alias <ALIAS> -keystore <PATH TO KEYSTORE> | "F:\api\openssl\bin\openssl.exe" sha1 -binary | "F:\api\openssl\bin\openssl.exe" base64
both the ALIAS and PATH TO KEYSTORE are same as the ones i use while exporting my application. Also the password I give is also the same i use while exporting my app.
I have properly updated the key on facebook on both dev n release options.
How ever when i try to share from my app it shows me a Toast containing following error:
(#404)Key hash <A COMPLETELY NEW HASH> does not match any stored key hashes.
Can anybody help me.
It generally means the app Id of that app you are using that doesn't have same hash key that you are using....
my solution would be
1.Create completely new app on Facebook and get new app id.
2.Generate hash key properly with your own debug.keystore file and put it into Facebook app
I was facing the same issue after doing this i got rid from
(#404)Key hash does not match any stored key hashes.
I might be repeating things you already know, but you need to add multiple key hashes to your app settings if you're doing development and release.
In general, when you're exporting your app (to put on the Play Store, for example), you're using the release keystore, whereas when you're doing development (building from IntelliJ or Android Studio), you're using the debug keystore. You need to put the key hash from both of these keystores in your app settings.
I have a problem when I want to publish my application android with fb integrated. I signed my app with eclipse, and used "keytool -exportcert -alias androidreleasekey -keystore MyReleaseKeystore.keystore | openssl sha1 -binary | openssl base64" in terminal to generate a release key, and I added in "Native Android App" configuration.
I tested l'app, and I got error when I wanted to login: " is misconfigured for facebook login.... "
When I tested with debugkey, all works well.
And When I generate the release key for FB, the keytool didn't ask me for the password. I think it should have?
is the "-alias androidreleasekey" should have a nother alias name? or juste whatever i like?
Any ideas? Thanks!
I've checked all the steps, everything is correct.
My problème appears just when app facebook is installed; when app facebook is not installed, everything works well.
I finished it by forcing all login FB by the browser, never by facebook app.
Thanks every one!
You must have given a wrong path to your keystore file, make sure your path is valid
as stated here : General Rule: If the tool does not ask for password, your keystore path is incorrect.
about the alias i'm pretty sure you should write the same one as you signed your app with .. because i've seen a different key is generated with different alias.
Follow these points and it's guaranteed to work:
Make sure the path to your keystore file is correct. The keytool command will generate a key even if the path is incorrect. How do you know it's correct? You are asked for a password.
The alias is critical. If you're not sure what the Alias is, export your apk once from within Eclipse (Right click project -> Android Tools -> Export signed application package). After you insert the password, you need to select an alias from the dropdown. Make sure this is exactly the same alias you should be using from the command line.
Copy the generated hash including the '=' sign at the end. and paste it to the facebook app console. Don't forget to click 'Save changes'.
I have integrated my application with Facebook, and for this I am using Facebook's Graph API. I am retrieving profile and friends information. It is working fine on my device which has Android 2.3 (Gingerbread), but recently my client has faced an issue while he is trying to connect to Facebook through my app. He has Android 4.0 (Ice Cream Sandwich) on his device. When he clicks a button on the app that takes him to the Facebook login screen, after login he gets a message:
My app is misconfigured for Facebook login. Press Okay to go back to the application without connecting to Facebook.
I am not getting what is the problem whether it is related to Android version or what.
How can I fix this problem?
I work at Facebook, and this is an important issue that needs to be addressed. The other answer for this question suggests that disabling SSO is very bad and will open up your app to malicious apps that can steal your user's Facebook credentials.
The hack launches a WebView dialog to Facebook without SSO, and the user must type their login credentials into that dialog. Malicious apps can then steal this information easily. It is always advised to implement Facebook SSO correctly to ensure that your app is secure and protect your user's sensitive data.
Prior to adding this error message, the dialog would automatically close without warning and fail silently. We added this error message to visually display that there is an issue with your app configuration in your Facebook app dashboard. For Android, if you check your LogCat, you'll see that after pressing "Okay", there should be an error message that will display a more technical description of what is causing the authentication to fail.
For example, if you use our Hackbook example and did not supply your own APP_ID in the source and did not add your hash key to the dashboard, you'll see this error in LogCat after pressing "Okay" in the native SSO dialog (if Util.ENABLE_LOG is set to true):
D/Facebook-authorize(24739): Login failed: invalid_key:Android key mismatch. Your key "uk3udeH7vrOGNFH2FJjdJbdWJWI" does not match the allowed keys specified in your application settings. Check your application settings at http://www.facebook.com/developers
We added the visual error message to help you. This, in theory, does not break previous implementations if it was implemented correctly to begin with. If you see this error message, that means you did not configure your app settings correctly on your dashboard.
Double check your Android Class/Package name, Android hash keys, etc. You will not see this message if you did everything correctly.
In summary, you are getting that error message because there is an issue with your app configuration, for example, a mismatch between the Android hash keys in your dashboard. Before Facebook added this error message, the dialog would launch, then automatically close and fail. To fix this, check your LogCat for any error messages and make sure that you have everything implemented correctly. You can read up on our documentation to make sure you have everything correct. Do not use the accepted answer for this question.
You can also follow the external bug report that a Facebook developer has reported for more updates.
Try to set it like this:
First download OpenSSL (if you have a 64-bit machine you must download openssl-0.9.8e X64, not the latest version, openssl-0.9.8k X64, because the output will not be valid). Extract your files, create the folder openssl, for example in C:/ and copy files there.
Find your path to keytoo. Mine is C:\Program Files\Java\jdk1.7.0_05\bin.
Find your path to debug.keystore. YHou can see what is path if you open in Eclipse, menu Window -> Preferences -> Android -> Build, and you will see Default Debug keystore:-and the path.
Find your path to openssl. Mine is C:\openssl8e\bin/.
Open cmd and type:
"C:\Program Files\Java\jdk1.7.0_05\bin\keytool" -exportcert -alias androiddebugkey -keystore "C:\Users\User.android\debug.keystore" | "C:\openssl8e\bin\openssl" sha1 -binary | "C:\openssl8e\bin\openssl" base64
Aand then press Enter.
Insert password: android
You will get your hash key for debug.keystore.
When you export a signed APK, and you create a keystore for the application, just replace in cmd debugkeystore alias with your alias for the app, the keystore path with the path to your newly created keystore for the app and insert the password for your app.keystore, and you will get a new hash key for your signed app.
The answer from Jesse Chen is fine. Facebooks SDK works fine, don't break it.
I again ran into this problem and found out that the Facebook SDK documentation is corrected and is very fine now. Now it is guiding how to debug and release hash keys can be set; just do as it says.
Below is my old story. There is missing that you can set two hash keys, one for debugging and one for signed, released application for the old Play Store.
I found out that problem was in my case in the Facebook SDK's documentation. It guided us to use the debug key hash and put it in Facebook's app configuration. Hash is guided to get this way:
keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64
This works fine, when you are dubugging or running application from Eclipse.
But, if you publish your application to Andoid Play, you must use your own publisher key to export the signed .apk file. With that .apk, the hash in the Facebook app console is not valid any more! You must get a hash for the developer key like this:
keytool -exportcert -alias <developer alias> -keystore ~/.android/<developer keystore> | openssl sha1 -binary | openssl base64
And put it in the Android Key Hash in the Facebook app console for your published application. After that, SSO works fine again for your signed .apk file.
From what I could gather, it's a Facebook problem and has been reported. But, the problem persists.
A way around this (tested on 2.3.3) is to hack on the Facebook SDK, seach for the 2 authorize methods and change the DEFAULT_AUTH_ACTIVITY_CODE to FORCE_DIALOG_AUTH. This will disable the Single Sign On feature.
If your prefer got to
public void authorize(Activity activity, String[] permissions,
int activityCode, final DialogListener listener)
and disable the startSingleSignOn part. It's preferable not to, because eventually Facebook will solve the problem, and you only have to put the old constant back.
EDIT
This solution raises security problems. Check Jesse Chen answer.
I faced the same problem, after spending 24 hours and a lot of search we use this method to solve my problem.
Check your Xcode project current bundle identifier
for example : com.yourcompanyname.yourappname
use the same com.yourcompanyname.yourappname bundle identifier for creating app in Facebook see attachment.
I had this problem just a few minutes ago myself on 4.0.4 and it seems to have resolved itself.
Although late, still useful:
*Here's the corerct way to do(for debug key, change accordingly for release):*
keytool -exportcert -alias androiddebugkey -keystore "C:\Users\<User>\.android\debug.keystore" > <Drive letter>:\debug.txt
openssl sha1 -binary "<Drive letter>:\debug.txt" > "<Drive letter>:\debug_sha.txt"
openssl base64 -in "<Drive letter>:\debug_sha.txt" > "<Drive letter>:\debug_base64.txt"
The hash is in the last generated file: debug_base64.txt....open it and copy the hash.
Remember to replace "" and with your username and drive letter of your choice
When you create the key hash, you might end up with something which has the equality sign "=" at the end, like ga0RGNYHvNM5d0SLGQfpQWAPGJ8=. While Facebook gladly accepts the equality sign as part of the key hash, you have to remove it in order for it to work.
Additionally, check out the accepted answer to Android Facebook SDK 3.0 gives "remote_app_id does not match stored id" while logging in: when getting the key hash for the debug keystore, use the password "android". Otherwise the key hash will be incorrect and you will get the error specified in the question (be nice and vote up the answer there if it helped you.)
Regarding apps signed with OWN keystore:
After spending several hours solving this issue, I finally got it and want to provide an answer for those who are still suffering:
My steps:
I signed my app via eclipse with my own keystore file (NOT debug.keystore).
Via command line and known commands (keytool -exportcert -alias -keystore ~/.android/ | openssl sha1 -binary | openssl base64) I successfulluy received the key hash.
Pasted the key hash in the dev dashboard,waited a few mins -> Still the same ERROR (as specified in the question above).
i tried several differend keytools, on several jdks, etc... nothing changed.
Solution:
I turned on debuggable in manifest, turned on debugging in facebook sdk. then i signed the apk with my own keystore and uploaded it on real device.
i connected device via usb and opened DDMS perspective to see logcat on device.
I started my app and let the error message occur.
It prints out a key totally different from the key generated by keytool. I took this key from logcat, pasted it to dev dashboard and voila -> EVERYTHING WORKS
I still don't know why this happens or what is causing the wrong key, but this way it works for me.
On Debian system like ubuntu use the keytool of java found under directory /usr/lib/jvm/jdk*.*.*/bin/keytool and generate like this
/usr/lib/jvm/jdk1.7.0/bin/keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64
This way you get the authentic hash key that can be put under your app hash of facebook.
Usually this problem could be solved with two check:
flag in the facebook console to publish live the facebook configuration
api key mismatches
I managed to solve the issue I was having with misconfigured for Facebook on Android by ensuring I had the correct hash key for a release version.
To get the release version hash key, find the key you used to sign the application and do the following, insert the name of your keystore alias (without brackets). If you don't know your alias this can be found by exporting your app as a signed app and the alias is on the second page of the wizard. Also insert the path to your keystore (without brackets).
keytool -exportcert -alias [Alias of your keystore] -keystore [Path to keystore] | openssl sha1 -binary | openssl base64
I did a Toast for exceptions and found it throws a key mismatch exception today added the key in the FB app page and it works fine
Also encountered this issue.
Simply go to the Facebook developers getting started page here
and follow step 4 - the thing with the command line.
Worked for me.
Enjoy.
I just had the same problem and the solution turned out to be super simple. When I created the app in the dashboard, I only had added the key hash for the android debug keystore. This all works fine if you install the app as a developer via a USB cable in this case.
Once you have an app in the Play Store, you will use a production key to sign the app. This also means, that you have to get the key hash of the production key like for the debug key and add it as a second hash to the list of native app hashes.
just to remember you how the key hash works:
keytool -exportcert -alias -keystore ~/keys/android_keystore | openssl sha1 -binary | openssl base64
Hope that helps!
I had a similar problem, but for iOS.
The solution is to do with configuring the Facebook app on the Facebook developer daskboard.
For iOS, 2 things must be done:
Enabled Facebook Login
Bundle ID must be the same as the app
It's a keystore issue..configure your eclipse to use the same keystore for which app was configured for.
I got the same error a few days ago. In my case it was due to an Android key mismatch. Here is how I fixed it if it may help you too:
Open Util.java in the Facebook SDK, set private static boolean ENABLE_LOG = true;. Now run your app and enter your email id and password. Facebook sends back a signature if there's a key mismatch. You'll find this key (signature) in LogCat. Just copy this key and paste it in the app dashboard. That should fix the problem. Remember to set private static boolean ENABLE_LOG = true; back to false.
When hitting the "debug"-button in eclipse my App gets signed by a debug key form android which is stored in the file "debug.keystore".
Now I am implementing the Facebook SDK which forces me to use a signed app for the Single SignOn feature. That way I need to generate the hash of my companies keystore and store the one in our facebook developer account.
I know how to sign an app through the wizard in Eclipse (over the AndroidManifest.xml). How to debug such a signed app?
Can I change the debug key somehow and set up our companies key as debug key? Or how should I go? Right now I can get FB working only by signing and installing my app on a device. I already tried to generate a hash of the debug key with no luck...
Just in case anyone wants to
change the debug key somehow and set up our companies key as debug key
as the original poster asks, you can do so using keytool as so:
STORE_PASS=<pass_of_company_store>
ALIAS=<alias_of_key_in_company_store>
ALIAS_PASS=<pass_alias>
keytool -importkeystore -v -noprompt \
-srckeystore /path/to/company/key -destkeystore debug.keystore \
-srcstorepass $STORE_PASS -deststorepass android \
-srcalias $ALIAS -destalias androiddebugkey \
-srckeypass $ALIAS_PASS -destkeypass android
You can then replace your debug (perhaps ~/.android/debug.keystore) with the new one that this generates, and eclipse will happily use it to build apks that can be fully debugged and accepted by facebook.
Note that you have to be very careful with this new debug.keystore. It cannot fall into the wrong hands or your app can easily be hijacked on the Google Play Store.
I do not recommend setting your companies key as your debug key, but you can do that by replacing the Eclipse debug keystore file, named debug.keystore. You can find its location on your OS by reading through this.
A better solution would be to generate the hash of the debug key - follow the instructions given on the official SDK for Android page, and make sure you mention the correct keystore file, and the alias "androiddebugkey". The password is always "android".