Skip to content

Instantly share code, notes, and snippets.

@calvinh8

calvinh8/CreateKeyHashes-Android.md

Last active February 26, 2021 09:12
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save calvinh8/43c06f3600c5d22d4c04bc1abf1774a6 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save calvinh8/43c06f3600c5d22d4c04bc1abf1774a6 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. Calvin renamed this gist Apr 5, 2018. 1 changed file with 0 additions and 0 deletions.
    0 CreateKeyHashes-Android → CreateKeyHashes-Android.md
    View file
    File renamed without changes.
  2. Calvin created this gist Apr 5, 2018.
    20 changes: 20 additions & 0 deletions CreateKeyHashes-Android
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,20 @@
    ### 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`