Skip to content

Instantly share code, notes, and snippets.

@calvinh8
Last active February 26, 2021 09:12
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save calvinh8/43c06f3600c5d22d4c04bc1abf1774a6 to your computer and use it in GitHub Desktop.
Save calvinh8/43c06f3600c5d22d4c04bc1abf1774a6 to your computer and use it in GitHub Desktop.

Facebook

Add your development and release key hashes To ensure the authenticity of the interactions between your app and Facebook, you need to supply us with the Android key hash for your development environment. If your app has already been published, you should add your release key hash too. You'll have a unique development key hash for each Android development environment. To generate a development key hash, on Mac, run the following command:

keytool -exportcert -alias androiddebugkey -keystore ~/.android/debug.keystore | openssl sha1 -binary | openssl base64

On Windows, run this command:

keytool -exportcert -alias androiddebugkey -keystore %HOMEPATH%\.android\debug.keystore | openssl sha1 -binary | openssl base64

This command will generate a 28-character key hash unique to your development environment. Copy and paste it into the field below. You will need to provide a development key hash for the development environment of each person who works on your app.

Google

Signing-certificate fingerprint Add your package name and SHA-1 signing-certificate fingerprint to restrict usage to your Android apps Learn more Get the package name from your AndroidManifest.xml file. Then use the following command to get the fingerprint:

keytool -exportcert -keystore path-to-debug-or-production-keystore -list -v

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment