SHA-1 release fingerprint

Get Started | Login

Discussion Forums > Plugins, Customizing, Source Code

Replies: 6 Views: 389

miku Aspiring developer Posts: 405 Reg: Feb 20, 2014 zagorje ob savi 10,600	confirm \| cancel 12/24/15 02:56 AM (8 years ago) SHA-1 release fingerprint My app worked when I used Eclipse, looks that now in Android Studio, SHA-1 is wrong. I tried to check SHA-1 with this help: http://stackoverflow.com/questions/27609442/how-to-get-the-sha1-fingerprint-certificate-in-android-studio-for-debug-mode How can I find SHA-1 release fingerprint, not debug? Title Comments My app worked when I used Eclipse, looks that now in Android Studio, SHA-1 is wrong. I tried to check SHA-1 with this help: http://stackoverflow.com/questions/27609442/how-to-get-the-sha1-fingerprint-certificate-in-android-studio-for-debug-mode How can I find SHA-1 release fingerprint, not debug?

Dusko Veteran developer Posts: 998 Reg: Oct 13, 2012 Beograd 22,680	12/24/15 04:25 AM (8 years ago) Well, I searched for "find SHA-1 release fingerprint, not debug" and I found this link among others: http://stackoverflow.com/questions/12214467/how-to-obtain-signing-certificate-fingerprint-sha1-for-oauth-2-0-on-android Seems full of advice for Eclipse in the beginning, but later on it turns to Android Studio too. Comments Well, I searched for "find SHA-1 release fingerprint, not debug" and I found this link among others: http://stackoverflow.com/questions/12214467/how-to-obtain-signing-certificate-fingerprint-sha1-for-oauth-2-0-on-android Seems full of advice for Eclipse in the beginning, but later on it turns to Android Studio too.

CMCOFFEE Android Fan Posts: 2017 Reg: Jan 04, 2013 Amarillo, Texas 26,670	12/24/15 06:03 AM (8 years ago) You have to have the same keystore you made in Eclipse and import in android studio. What it sounds like you're doing is creating a new one Comments You have to have the same keystore you made in Eclipse and import in android studio. What it sounds like you're doing is creating a new one

miku Aspiring developer Posts: 405 Reg: Feb 20, 2014 zagorje ob savi 10,600	12/25/15 05:15 AM (8 years ago) I tried several ways to get release fingerprint, but no matter which I try, I always get the same result, SHA-1 is always the same like that one in Eclipse. But result of my Location Map is blank Google map: https://www.dropbox.com/s/m9rv4w8rtk48b4k/screen_gmap1.png?dl=0 Comments I tried several ways to get release fingerprint, but no matter which I try, I always get the same result, SHA-1 is always the same like that one in Eclipse. But result of my Location Map is blank Google map: https://www.dropbox.com/s/m9rv4w8rtk48b4k/screen_gmap1.png?dl=0

CMCOFFEE Android Fan Posts: 2017 Reg: Jan 04, 2013 Amarillo, Texas 26,670	12/25/15 07:12 PM (8 years ago) What steps have you done? Comments What steps have you done?

miku Aspiring developer Posts: 405 Reg: Feb 20, 2014 zagorje ob savi 10,600	12/26/15 02:13 AM (8 years ago) 1. I created new keystore 2. I checked SHA-1 and it showed me debug keystore SHA-1 number with this: - Click on Gradle (From Right Side Panel, you will see Gradle Bar) - Click on Refresh (Click on Refresh from Gradle Bar, you will see List Gradle scripts of your Project) - Click on Your Project (Your Project Name form List (root)) - Click on Tasks - Click on android - Double Click on signingReport (You will get SHA1 and MD5 in Run Bar) It shows debug keystore: :app:signingReport Variant: debug Config: debug Store: /Users/milan/.android/debug.keystore Alias: AndroidDebugKey MD5: ………. SHA1: ……… 4. I went to Google Developers Console and created new project, enabled API button on Google Maps Android API v2, created Android key with debug SHA1. New API key goes to Manifest. I created new release apk then. 5. I need release.keytore I tried with this: - In my Java directory I enter in command prompt (on Windows) or Terminal (Mac) keytool -list -v -keystore YOUR_KEYSTORE_NAME -alias YOUR_ALIAS_NAME I entered password and alias name and it shows me SHA-1, but exactly the same number as debug. Comments 1. I created new keystore 2. I checked SHA-1 and it showed me debug keystore SHA-1 number with this: - Click on Gradle (From Right Side Panel, you will see Gradle Bar) - Click on Refresh (Click on Refresh from Gradle Bar, you will see List Gradle scripts of your Project) - Click on Your Project (Your Project Name form List (root)) - Click on Tasks - Click on android - Double Click on signingReport (You will get SHA1 and MD5 in Run Bar) It shows debug keystore: :app:signingReport Variant: debug Config: debug Store: /Users/milan/.android/debug.keystore Alias: AndroidDebugKey MD5: ………. SHA1: ……… 4. I went to Google Developers Console and created new project, enabled API button on Google Maps Android API v2, created Android key with debug SHA1. New API key goes to Manifest. I created new release apk then. 5. I need release.keytore I tried with this: - In my Java directory I enter in command prompt (on Windows) or Terminal (Mac) keytool -list -v -keystore YOUR_KEYSTORE_NAME -alias YOUR_ALIAS_NAME I entered password and alias name and it shows me SHA-1, but exactly the same number as debug.

Dusko Veteran developer Posts: 998 Reg: Oct 13, 2012 Beograd 22,680	12/30/15 01:44 PM (8 years ago) Have a look at this: https://www.buzztouch.com/forum/thread.php?tid=D7E9D9B86215CAD0726C64C Comments Have a look at this: https://www.buzztouch.com/forum/thread.php?tid=D7E9D9B86215CAD0726C64C

Login + Screen Name Required to Post Login to participate so you can start earning points. Once you're logged in (and have a screen name entered in your profile), you can subscribe to topics, follow users, and start learning how to make apps like the pros.