Facebook key hash, android keystore confusion

Question

keytool -exportcert -alias mykeystore -keystore mykeystore| openssl sha1 -binary | openssl base64

Hi, I am using the above command to generate a hash of the facebook key. It asks for my password and gives me the key hash. I put this key hash in the settings of the facebook application, but it does not work for my signed Android application.

When I debugged the Android application, I saw a console message saying that it did not recognize the “hash key”, so I copied “blahblahblah” to the facebook application and it worked - my Android application could use the facebook stuff in debug mode. But it is clear that this was only for debug storage. Now for the real keystore, the one that it creates is still not so, so the production version of my application will not be able to use facebook api.

One thing in my keystore is that it was done in an eclipse. This is a single keystore with two keys in it. I noticed that keystore eclipse does not act like it does on the command line, and that they are incompatible for signing. However, I have already released a version of my application, so I need to execute the corresponding keys that I already use.

Insight is appreciated.

Answer 1

Use keytool -list to list your aliases. If you are not sure which one you signed the APK that you released, try both. Need to work.

Answer 2

I had the same problem - the debug hash key worked, but the production key did not. I finished installing OpenSSL from a different source than I originally installed, re-created the hash key, and fixed the problem. This is the site I worked on OpenSSL on: http://gnuwin32.sourceforge.net/packages/openssl.htm .

Answer 3

When running Cygwin on Windows, use cygpath to search for the keystore:

 keytool -exportcert -alias androiddebugkey -keystore $(cygpath -aw ~/.android/debug.keystore) | openssl sha1 -binary | openssl base64 Keystore-Kennwort eingeben: android 

When using / cygpath / c / Users / name / ... this will not work.