Facebook Login for Android App with release key

android, facebook, facebook-graph-api

Solution

Here is what I did that solved the problem:

- Used openssl-0.9.8e_WIN32 Instead of openssl-0.9.8k_WIN32

- I was not using alias in the following or maybe I was entering a space in the alias because of which the key which was generated was wrong.

I used this instead:

keytool -exportcert -alias <aliasNameUseInReleaseKeystore> -keystore <ReleasekeystoreFilePath> | openssl sha1 -binary | openssl base64

P.S. The method which I have posted in my question is really useless. It did nothing more than confuse me to no end.

Problem

I am trying to release my app on Google Play. I have a Facebook login in my app. Up until yesterday all was working fine till the time I was running the application with `debug.keystore`. But when I use my own release key and sign my application Facebook doesn't login and I cant seem to figure out why. Followed this link and did all that was meth as well : so : key-hash-for-android-facebook-app I changed machines, I changed platforms (windows and mac osx ML) as well to get a solution but the same issue. IT DOES NOT LOG IN. The below code gives me the proper hash key when i use debug.keystore where as when i sign the application even with different keys I get the same Hashkey ( which I have come to a conclusion after lots of trials that the key i get is wrong) ``` PackageInfo info; try { info = getPackageManager().getPackageInfo("com.you.name", PackageManager.GET_SIGNATURES); for (Signature signature : info.signatures) { MessageDigest md; md = MessageDigest.getInstance("SHA"); md.update(signature.toByteArray()); String something = new String(Base64.encode(md.digest(), 0)); //String something = new String(Base64.encodeBytes(md.digest())); Log.e("hash key", something); } } catch (NameNotFoundException e1) { Log.e("name not found", e1.toString()); } catch (NoSuchAlgorithmException e) { Log.e("no such an algorithm", e.toString()); } catch (Exception e) { Log.e("exception", e.toString()); } ``` So is there any kind of extra steps which we need to take when signing the application with the release key. Please HELP.

Original source

Related problems