Tech Tips & Tricks

How To Get Facebook KeyHash For Your Android App

Make sure you have OpenSSL installed. If not, download and install it to your desktop according to either 32 or 64 version.

Once installed, make sure that it is part of the system path so you can execute OpenSSL anywhere.

To get the key hash of your Android app, go to where your keystore file is located and type the following.

keytool -list -alias [ALIAS_NAME] -keystore [KEYSTORE_FILE] | openssl sha1 -binary | openssl base64

That’s it!

Google Play Service Test Account Does Not Work When Deployed To Android

So yeah, here is the thing. The Google Play Service documentation enables you to add test accounts to test your app when they are not yet published.

I had been looking for ways to do the same even if the game or its game services are published but to no avail.

Heck, publish or unpublished, the test accounts were unable to log in. It would also be quite a hassle to manually export the Android app to APK and install it into the device or emulator just to debug.

It took my quite some time to find the right keywords in my Google search that I was able to find a solution to this.

Use your release certificate as your debug certificate. But how?! Good question. In Eclipse, you can set a custom debug key by going to Preferences > Android > Build and selecting the keystore file of your choice, in this case the release keystore.

Problem is, you will encounter an error message that says “Keystore was tampered with, or password was incorrect”.

There are 3 things to consider why this happens:

• The keystore password must be “android”
• It must contain a key named “androiddebugkey”
• The key’s password must be “android”

I know you came upon this post to look for a solution so I will stop here because I am sure you do not care the explanations so long as you are able to convert your release keystore into the debug keystore.

To do so, type:

keytool -importkeystore -v -srckeystore [your_release.keystore] -destkeystore [your_new_keystore_filename] -srcstorepass [your_release-pass] -deststorepass android -srcalias [your_release-key] -destalias androiddebugkey -srckeypass [your_release-pass] -destkeypass android

That’s it. Select the new debug keystore and clean and rebuild your Android project. That should do the trick.

How To Fix The Debug Certificate Expired Error In Eclipse Android

After you install the Android SDK in Eclipse, it generates a debug signing certificate for you in a keystore called debug.keystore. The Eclipse plug-in uses this certificate to sign each application build that is generated.

Now, the problem with this debug certificate is that it is only valid for a year, or 365 days. If your Eclipse IDE uses an expired debug certificate, you will not be able to create and/or deploy an Android app.

To fix this problem all you need to do is delete the debug.keystore file.

1. Go to Preferences
2. Android
3. Build
4. Default debug keystore

There you should see the folder where the file is located. Simply delete that file and you are good to go.