There are many ways to get the SHA1 fingerprint; here are few examples:
1. Go to your java bin directory via the cmd:
C:\Program Files\Java\jdk1.7.0_25\bin>
Now type in the below comand in your cmd:
Then you should get your results :)
2. From a Debug Keystore we can get the SHA1 value in
1. Go to your java bin directory via the cmd:
C:\Program Files\Java\jdk1.7.0_25\bin>
Now type in the below comand in your cmd:
keytool -list -v -keystore c:\users\your_user_name\.android\debug.keystore -alias androiddebugkey -storepass android -keypass android
2. From a Debug Keystore we can get the SHA1 value in
Eclipse
. Accessing from the menu:Window
->Preferences
->Android
->Build
but it doesn´t work for a production
So, to get the SHA1 value from a production Keystore go to:
3. To get the SHA1 for ClientID for Sign In with Google+ and more actions:
General Form:
For Release, replace with your keystore path and alias password, for Example :
Keystore
.
So, to get the SHA1 value from a production Keystore go to:
Android Tools
-> Export Signed Application Package
. Follow the process for signing your apk and the SHA1 will showed as a certificate.3. To get the SHA1 for ClientID for Sign In with Google+ and more actions:
General Form:
keytool -list -v -keystore <your_keystore_full_path> -alias <your_alias_name>
For Debug, replace with your debug.keystore path, for Example :
keytool -list -v -keystore C:\Users\DAVID\.android\debug.keystore -alias androiddebugkey
Password: androidFor Release, replace with your keystore path and alias password, for Example :
keytool -list -v -keystore C:\ProjectsData\keystore\my-release-key.keystore -alias alias_name
Password: Your alias password.
No comments:
Post a Comment