Develop Reference

Keystore file does not exist: /root/.android/debug.keystore for ubuntu

Need google+ sign in for my phonegap application for that I want to generate Certificate SHA-1.I run
keytool -exportcert -list -v \
-alias androiddebugkey -keystore ~/.android/debug.keystore
the command to generate Android Signing Certificate SHA-1, but it gave an error
Keystore file does not exist: /root/.android/debug.keystore
so I search for that file using find ~ -name "debug.keystore" but my search result is empty.
I also tried below command
keytool -genkey -alias myKey -keystore store.jks
keytool -selfcert -alias myKey -keystore store.jks
but i didn't found Android Signing Certificate SHA-1

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
Try this command. Your debug keystore is always present in /home/<username>/.android and ~ is just a shorthand for /home/<username>.
If your SDK is installed properly, there should be no issues in running that command. Otherwise, we'll need some more information to find and fix the issue.
If PhoneGap/Meteor has its own set of android bundles, you might want to try something on these lines
keytool -list -v -keystore ~/.meteor/android_bundle/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

You don't have to use the debug certificate, just create a new certificate by following this tutorial and use it to sign your debug and release versions of the app.

What is production keystore in android and how can I get the path-to-production-keystore?

I am trying to add google authentication feature in my android app and for that I need to get the Android Signing certificate SHA-1. The official tutorial says to use the below command to get the SHA-1 hash value .
In release mode
keytool -exportcert -list -v \-alias <your-key-name> -keystore <path-to-production-keystore>
debug mode
keytool -exportcert -list -v \-alias androiddebugkey -keystore ~/.android/debug.keystore
Now I am confused with what is this production-keystore and debug.keystore and how to get the path to production-keystore? Explanations are appreciated.

Please use below command for linux, if you don't have keystore file:
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
Production keystore will generate when you are creating signed APK file.
Refer below link for information:
http://developer.android.com/tools/publishing/app-signing.html

Stumble upon this but I was using Windows. I got my answer hoping to help other Windows user who came to this post.
keytool -list -v -alias androiddebugkey -keystore C:\Users\<name>\.android\debug.keystore

How to generate production sha1 key for Android?

I am building an android application where I am using google login. I earlier I have generated debug sha1 certificate key and it was working fine used below code - keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
Now I need to generate production. Could anyone help me to figure this out how to generate SHA1 key for production release.

Certificate fingerprint (SHA1) should I change it with release Certificate?

I am new to Google Play Game Services and recently managed to include it to an app. I generated a Certificate fingerprint with a terminal using this commant on MAC to test it:
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
My question is, when I upload my app to my dev account, should I change the certificate from debug to release? If yes, how can I do that?
is it using the same command but instead of "debug.keystore" -> release.keystore?

Yes, you will need to change it. See that your using androiddebugkey. When you release the app you will need to sign the app and then use the same key to generate the certificate.
If you using Android Studio, you can easily create a new key store and a new key alias. (Build -> Generate Signed APK)
Generate the release Certificate:
keytool -list -v -keystore ~/MyPath/my.new.keystore -alias mynewalias -storepass keystorepassword -keypass aliaspassword
EDIT: List the certificate fingerprints (SHA1, MD5) using this command line:
keytool -v -list -keystore yourkeystore -alias youralias

Android: Released vs Debug Fingerprint (Sha1)

I was trying to obtain my Sha1 fingerprint for release and debug. Fortunately, I was able to obtain the debug version code through
keytool -list -alias androiddebugkey -keystore C:\Users\Name.android\debug.keystore -storepass android -keypass android
I was wondering how I would get the release? I tried
keytool -list -alias androidreleasekey -keystore C:\Users\Name.android\debug.keystore -storepass android -keypass android
but unfortunately it came out as keytool error: java.lang.Exception: Alias <androidreleasekey> does not exist.
*Actually my result may have been my released key store since I already built it as released app... I'm not entirely sure though.

You need to find the location of the release keystore file and the name of the alias that you used to build your app.
To do this in Android Studio select Build > Generate Signed APK. You should see a dialog similar to below.
Get the location of the full file path for the release keystore from the Key store path. Then use this path along with the Key alias that is listed to get the SHA1 as you tried previously:
keytool -list -alias myappsalias -keystore
C:\users\dell-laptop\AndroidStudioProjects\myapp\myapp_release.keystore -storepass android -keypass android