To generate debug SHA1 fingerprint certificate, you first need to know the location of your debug.keystore file.Generating the debug SHA1 fingerprint certificate After you execute this command, you will be asked for you alias name, so remember the alias name that you created in the first step and input that alias name, and bingo you have for release SHA1 Fingerprint certificate.Ģ.In the command above, you need to replace the keystore_name with the path of the keystore you had created in the first step.Usually it’s located at C:Program FilesJavajdk1.8.0_11bin. You need to run this command from the bin directory of your java installation folder. keytool -list -keystore keystore_path.jks.Once you’ve generate the signed apk you can easily find out your SHA1 fingerprint using the keytool command –.

Here’s more information about generating signed apk. You may choose an existing keystore or create a new one, remember the alias name, as you might need it later. You can choose the generate signed apk option from build menu in Android Studio. Before generating the release certificate, you need to first generate signed apk.Generating the release SHA1 fingerprint certificate SHA1 fingerprint using command line windowsġ. Here’s how to get the SHA1 fingerprint certificate for both Release and Debug mode in Android. You need to sign your app with Release certificate before publishing. Do not publish apps that are singed in debug mode. You need to sign your app in Debug mode just for testing purposes.

There are two types of fingerprint certificates in Android, one is Debug and the other is Release.

Android studio debug certificate sha1