Now it will Ask Key Store Password, provide yours and press Enter to get your SHA1 and MD5 Certificate keys. Now add this SHA1 key to the google developers console in credentials tab and also change the build variants in android studio to release mode. SHA1(Secure Hash Algorithm 1) hash value is typically rendered as a hexadecimal number, 40 digits long used by the organizations like Google, Facebook etc uses SHA-1 hash value for secure connection between their services and clients. SHA-1 value of debug will be different from SHA-1 value of release build. How to Obtain SHA1 1) Open Android Studio.

The MD5 or SHA1 signature of a Xamarin.Android app depends on the.keystore file that was used to sign the APK. Typically, a debugbuild will use a different .keystore file than a release build.

For Debug / Non-Custom Signed Builds

Xamarin.Android signs all debug builds with the same debug.keystorefile. This file is generated when Xamarin.Android is firstinstalled.The steps below detail the process for finding the MD5 orSHA1 signature of the default Xamarin.Android debug.keystore file.

Locate the Xamarin debug.keystore file that is used to sign theapp. By default, the keystore that is used to sign debug versions ofa Xamarin.Android application can be found at the followinglocation:

C:UsersUSERNAMEAppDataLocalXamarinMono for Androiddebug.keystore

Information about a keystore is obtained by running the keytool.execommand from the JDK. This tool is typically found in the following location:

C:Program Files (x86)JavajdkVERSIONbinkeytool.exe

Add the directory containing keytool.exe to the PATH environment variable.Open a Command Prompt and run keytool.exe using the following command:

When run, keytool.exe should output the following text. The MD5: and SHA1: labels identify the respective signatures:

Locate the Xamarin debug.keystore file that is used to sign theapp. By default, the keystore that is used to sign debug versions ofa Xamarin.Android application can be found at the followinglocation:

~/.local/share/Xamarin/Mono for Android/debug.keystore

Information about a keystore is obtained by running the keytoolcommand from the JDK. This tool is typically found in the followinglocation:

/System/Library/Java/JavaVirtualMachines/VERSION.jdk/Contents/Home/bin/keytool

Add the directory containing keytool to the PATH environment variable.Open a Terminal and run keytoolby using the following command:

When run, keytool should output the following text. The MD5: and SHA1: labels identify the respective signatures:

For Release / Custom Signed Builds

The process for release builds that are signed with a custom.keystore file are the same as above, with the release.keystore file replacing the debug.keystore file that is usedby Xamarin.Android. Replace your own values for the keystore password,and alias name from when the release keystore file was created.

When the Visual Studio Distributewizard is used to sign a Xamarin.Android app, the resulting keystore resides in the following location:

C:UsersUSERNAMEAppDataLocalXamarinMono for AndroidKeystorealiasalias.keystore

For example, if you followed the steps in Create a New Certificate to create a new signing key, the resulting example keystore resides in the following location:

C:UsersUSERNAMEAppDataLocalXamarinMono for AndroidKeystorechimpchimp.keystore

For more information about signing a Xamarin.Android app, seeSigning the Android Application Package.

When the Visual Studio for Mac Sign and Distribute..wizard to sign your app, the resulting keystore resides in the following location:

~/Library/Developer/Xamarin/Keystore/alias/alias.keystore

For example, if you followed the steps in Create a New Certificate to create a new signing key, the resulting example keystore resides in the following location:

~/Library/Developer/Xamarin/Keystore/chimp/chimp.keystore

For more information about signing a Xamarin.Android app, seeSigning the Android Application Package.

I have shifted myself from Eclipse to Android Studio. Now I am trying to work on my Map app. So I need my SHA-1 fingerprint certificate number.

When I was using Eclipse it was right under Windows -> Preferences -> Android -> Build. But in Android Studio I couldn’t find out any option like this so that I could find easily the fingerprint. I am using Windows. I have read from this link that:

Android Studio signs your app in debug mode automatically when you
run or debug your project from the IDE.

So I tried to run this in command line after setting my Java bin path from this link and unfortunately couldn’t find my fingerprint. It is saying that it is an illegal option.

Is there a way to find the SHA-1 fingerprint from Android Studio like it was very easy in Eclipse? As I am newbie in Android Studio, what is the full process to find it?

Another thing I want to add is that I have my Eclipse generates the SHA-1 fingerprint and previously I have my app registered on that fingerprint in Google developer console, and I worked on that app in Eclipse by that API key. Is the same API key can be worked on this my project in Android Studio?

Easiest ways ever:

Update added for Android Studio V 2.2 in last step

There are two ways to do this.

1. Faster way:

1. Open Android Studio
2. Open your Project
3. Click on Gradle (From Right Side Panel, you will see Gradle Bar)
4. Click on Refresh (Click on Refresh from Gradle Bar, you will see List Gradle scripts of your Project)
5. Click on Your Project (Your Project Name form List (root))
6. Click on Tasks
7. Click on Android
8. Double Click on signingReport (You will get SHA1 and MD5 in Run Bar(Sometimes it will be in Gradle Console))
9. Select app module from module selection dropdown to run or debug your application

Check the screenshot below:

2. Work with Google Maps Activity:

1. Open Android Studio
2. Open Your Project
3. Click on File menu -> Select New -> Click on Google -> Select Google Maps Activity
4. A dialog would appear -> Click on Finish
5. Android Studio would automatically generate an XML file named with google_maps_api.xml
6. You would get debug SHA1 key here (at line number 10 of the XML file)

Check Screenshot below:

Android Studio V 2.2 Update

There is an issue with Execution.

Solution:

• Click on Toggle tasks execution/text mode from Run bar

Check Screenshot below:

Done.

My problem is the same as I have also shifted my Google Maps project from Eclipse to Android Studio. I have solved my problem by following this:

Go to your Java bin directory via the command:

Don’t be one of them. Why Email Signature is necessary?Every 2 out of 5 people are not aware of the basic principles of creating an impressive, informative signature. Free email signature generator for mac.

Now type in the below command in your command window (CMD.EXE):

Example:

Or you can just write this in cmd if you don’t know the username:

And you will get the SHA1.

Then I created a new key from https://code.google.com/apis/console because of my package name got changed and then use this key in my application. It works fine.

Make sure you are in BIN folder of jdkX.X.X_XX (my folder name is jdk1.7.0_71), or else if you don’t know what folder name you have then find it by opening the Java folder, and you will see what the folder name is, but you must be in your BIN folder and then run this command. Today I have got my SHA1 value in a cmd command window by the above procedure.

SNAPSHOT:

I just found the case to get SHA-1 in Android Studio:

1. Click on your package and choose New -> Google -> Google Maps Activity
2. Android Studio redirects you to google_maps_api.xml

And you will see all you need to get google_maps_key.

For Mac, this worked perfectly:

Photoshop dds plugin mac. (A Google search landed me here.)

The best solution for generating an SHA-1 key for Android is from Android Studio.

Click on Gradle on the far right side:

Click on the refresh icon, and you will see the name of the app:

Click on Tasks -> Report -> Signing Report:

Find the SHA-1 key on the bottom part in the console:

[Updated 2017]

Step 1: On Top Right side of Android Studio Click On Gradle option.

Step 2:

— 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 Gradle Console/Run Bar)

Step 3: Click on the Gradle Console option present bottom of Android Studio to see your SHA1 Key.

Step 4: Now you got the SHA key but you can’t run your project.That is why Change your configuration to app mode. See image below.

Like this.

Step 5: Happy Coding!!

i am going with @Hiren Patel answer but slightly change in android studio 2.2

I directly used the following command from my Mac using the terminal. I got SHA1 Finger. This is the command:

It’s very very easy in Gnu/Linux – Mac – Windows

First: – copy this command

Second: Now copy and paste the command in the terminal the Android Studio

Result!

Good Luck!!

For getting SHA1 for a production keystore:

1. Build –> Generate Signed APK…

2. Create keystore with password and follow the steps

3. Go to your Mac/Library/Java/JavaVirtualMachines/jdk1.8.0_20.jdk/Contents/Home/bin and drag the bin folder to the terminal after cd command to point at it so you can use the keytool tool. So, in terminal write cd (drag bin here) then press enter.

4. Then, copy and paste this in the terminal:

   Erase my path and go where you stored your keystore and drag your keystone and drop it after -keystore in the command line so the path will get created.

   Also, erase Your_keystore_AliaseName to put your alias keystone name that you used when you created it.

5. Press Enter and enter the password 🙂

6. When you enter the password, the terminal won’t show that it receives keyboard entries, but it actually does, so put the password and press Enter even if you don’t see the password is typed out.

If you have Android Studio then it is very very simple. Just create a MapActivity using Android Studio and after creating it go into google_maps_api.xml. In there there will be a link given in comments. If you paste it in your browser, it will ask a few details to be filled in and after that your API will be generated. There is no need of using keytool and all.

Screen shot:

If you are using Android Studio, you can get the SHA-1 and MD5 certificate fingerprint (debug, release… all Build Types!!) fast through Gradle Tasks:

signingReport

The SHA-1 and MD5 certificates are shown in Messages Logs.

Android Plugin (configured in the Gradle app) creates a debug mode for default.

com.android.application

File route to keystore:

I recommend to attachdebug.keystore to build.gradle. To do this put a file, debug.keystore, in an app folder and then Add SigningConfigs in Gradle app:

Extra: If you want creates for release, put a file, release.keystore, in an app folder. (This example uses the same debug.keystore.)

For Windows 10, from the Android Studio terminal:

Note: For the debug.keystore, the password is “android”. The debug keystore is typically located at '%USER_PROFILE%'/.android/debug.keystore.

I want to add one thing with the answer given by Softcoder. I have seen some people couldn’t give their debug.keystore path correctly on the command line. They see that they are doing the exact process accepted above, but it is not working. At that point try to drag the debug.keystore and drop it on the command line. It will help if the accepted answer is not working for you. Do the full process without any hesitation. It was a nice answer.

Use simple command:

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

and you will get the SHA1 key.

I found a very easy process to find you MD5, SHA-1 fingerprint using
Android Studio.

1. Run your project
2. Go to Gradle Menu (Menu: View -> Tool Windows -> Gradle)
3. Go to ‘signingReport’ in Gradle window. (Your project -> Tasks -> android -> signingReport)
4. Run it. (Using double-click or Ctrl + Shift + F10)
5. In Run window you will find all info.

It’s work only for debug mode. In realease mode I can not see sha-1.
Here result of gradlew signingReport

So I must use keytool to get sha-1. Here official Firebase doc:

Click the Gradle icon on the right panel, then click on the (root).

Tasks > android > signingReport

Then the Gradle script will execute, and you will see your keys.

This worked in my case: Use %USERPROFILE% instead of giving path .keystore file stored in this path automatically C:Users/user name/.android:

I do it this way:

Step 1: Go to this folder

On Mac: /Users//.android/

On Windows: C:Documents and Settings.android

On Linux: ~/.android/

Step 2: Run this command line:

You will see the SHA-1 key.

Use the instructions from the API Manager using keytool:

Get the package name from your AndroidManifest.xml file. Then use the
following command to get the fingerprint:

keytool -list -v -keystore mystore.keystore

When creating a new “Google Maps Project”, in Android Studio V 1.5.1, the last screen opens the google_maps_api.xml file and displays the screen with instructions as follows:

Resources:

TODO: Before you run your application, you need a Google Maps API key.

To get one, follow this link, follow the directions and press “Create” at the end:

https://console.developers.google.com/flows/enableapi?apiid=maps_android_backend&keyType=CLIENT_SIDE_ANDROID&r= YOUR SHA-1 + YOUR PACKAGE NAME

You can also add your credentials to an existing key, using this line:
YOUR SHA-1:YOUR PACKAGE NAME

Alternatively, follow the directions here:
https://developers.google.com/maps/documentation/android/start#get-key

Once you have your key (it starts with “AIza”), replace the “google_maps_key” string in this file.
<string name='google_maps_key' templateMergeStrategy='preserve' translatable='false'>YOUR GOOGLE MAPS KEY</string>

To get YOUR GOOGLE MAPS KEY just cut and paste the URL link given into your browser and follow the instructions above at the time of creating the new application. The SHA-1 and Package names are already in the link given so you do not need to know them. They will however be in your project in the resources>Values>google_maps_api.xml file which is completed when you follow the instructions on creating the project.

This worked for me:

Put path-to-debug-or-production-keystore here like C:usersyouruser.androiddebug.keystore -list -v

Make sure you already are in the Javajdk*bin directory in a command or terminal window.

Then use Android as the password.

Sometimes web resources could be misleading. These are the ones working:

If you need SHA1 for Google Maps, you can just see your error log in LogCat.

Go to File > Project Structure
Select ‘app’ or ‘mobile’ whatever you gave the name from ‘Modules’
Choose ‘Signing’ tab.

You can add certificate clicking on the ‘+’ button.

The easiest way to get the finger print is to switch from app to signed report by clicking the drop down and click build.

Then you will be able to see the sha1 fingerprint at the bottom pane where you see the debug report and stack trace. N.B remember to switch back to app when you want to run your app on a device or an emulator.

You can use following command and change AJAY SUNDRIYAL with your system name.This is only for your debug.keystore.This will work for you.

The path of the keystore is in double quotes. It is working fine.

1. Click on Gradle Icon in Right Pane.
2. Click on Root Project Name.
3. Click Tasks
4. Click Android
5. Click signingReport
6. in bottom pane where you see Run report
7. Click “Toggle Tasks Execytions/text mode”
8. you can see the sha-1

Tags: android