How to Get Md5 from Debug.Keystore File

How to get MD5 from debug.keystore file?

When I did it I used this.

keytool -list -alias androiddebugkey -keystore debug.keystore -storepass android -keypass android -v

Looks like your keystore file isn't correct.

How to get MD5 from debug.keystore file on mac

if you use a Mac or Linux OS, I've discovered that you'll find the debug.keystore file at: ~/.android/.

Android MD5 debug fingerprint missing from debug keystore

I found the answer. There is another post on SO (Link) that states that rolling back from

jdk-7-ea-bin-b140-windows-x64

to

jdk-6u25-windows-x64

resolves the issue. THIS WORKED FOR ME!

dranfi, your answer is technically correct, but that's what I used in the first place.

jdk-7-ea-bin-b140-windows-x64 obviously has some issues to resolve.

I perhaps should have stated the javaSDK version in the first place -sorry!

How do I generate my MD5 and SHA1 thumbprints using eclipse for debug keystore (Android)

get your sha1 and md5 thumbprint for debug keystore (also works for your other keystores).
Go to you package exporler in eclipse (defaults to the left side) right click it>android tools>export signed application package

Then navigate to your debug keystore normally in your .android folder and select it

Then enter the password which is "android" with no quotes

Next it will ask for an alias click the drop down list and select androiddebugkey and again, enter android as the password.

Next if you scroll down it will show the MD5 and SHA1 thumb print if you scroll down

then just cancel and use it how you want if you want your hash key just paste this under your onCreate

REPLACE "com.you.name" to your application package name.

PackageInfo info;
try {

    info = getPackageManager().getPackageInfo( "com.you.name",PackageManager.GET_SIGNATURES);

    for (Signature signature : info.signatures)
    {
        MessageDigest md;
        md = MessageDigest.getInstance("SHA");
        md.update(signature.toByteArray());
        String something = new String(Base64.encode(md.digest(), 0));
        //String something = new String(Base64.encodeBytes(md.digest()));
        Log.e("Hash key", something);
    }

} catch (NameNotFoundException e1) {
Log.e("name not found", e1.toString());
} catch (NoSuchAlgorithmException e) {
Log.e("no such an algorithm", e.toString());
} catch (Exception e) {
Log.e("exception", e.toString());
}

How to generate SHA1, SHA256, MD5 for default debug key using keytool in Mac, Windows and Linux?

Following will give you SHA1, SHA256, MD5 for default debug key.
And it can be used for developing and debugging with google play services.

Linux & Mac command

keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android

Windows

keytool -exportcert -keystore C:\Users\<USERNAME>\.android\debug.keystore -list -v

Replace with your windows account name example:

keytool -exportcert -keystore C:\Users\Aakash\.android\debug.keystore -list -v

If asked password, type: android

cant get MD5 Fingerprint of the SDK Debug Certificate

Get rid of the backslashes if you are typing this all on one line. Hence, it should look like:

keytool -list -alias androiddebugkey -keystore debug.keystore -storepass android -keypass android

(assuming you are running this in the directory where your debug keystore resides, which is ~/.android on Ubuntu)

Getting the MD5 Fingerprint of the SDK Debug Certificate

open eclipse path--click window-preferences-android-build path--/home/name/.android/debug.keystore

open the terminal--cd /home/name/.android/
copy the keytool and paste it.
you get the MD5 certificate and put into the xml file and run the application in google api device..

 keytool -list -alias androiddebugkey -keystore debug.keystore -storepass android -keypass android

(assuming you are running this in the directory where your debug keystore resides, which is ~/.android on Ubuntu)

How to find the MD5 fingerprint of my Android App

You will be needing two keystores.

One for debug purpose and
One for release purpose.

While you are developing your application via eclipse and debugging it on simulator or device. You will be needing debug keystores. Otherwise you will not be able to see the map.
debug keystore is already present into your system.

Try finding them at

Windows Vista: C:\Users\<user>\.android\debug.keystore

Windows XP: C:\Documents and Settings\<user>\.android\debug.keystore

OS X and Linux: ~/.android/debug.keystore

Open console/terminal on to the above location where debug.keystore file is present and execute

keytool -list -keystore debug.keystore

Output will be like (press simply enter when password is asked)

rohit@Desktop:~/.android$ keytool -list -keystore debug.keystore
Enter keystore password:  

*****************  WARNING WARNING WARNING  *****************
* The integrity of the information stored in your keystore  *
* has NOT been verified!  In order to verify its integrity, *
* you must provide your keystore password.                  *
*****************  WARNING WARNING WARNING  *****************

Keystore type: JKS
Keystore provider: SUN

Your keystore contains 1 entry

androiddebugkey, 19 Apr, 2011, PrivateKeyEntry, 
Certificate fingerprint (MD5): 00:35:C2:48:65:43:CG:55:41:11:16:F1:4C:11:82:C5
rohit@Desktop:~/.android$ 

Copy this MD5 fingerprint value and go to

http://code.google.com/android/maps-api-signup.html

You will get Map Keys On successful signup. Put those in the MapView Element of your view.

For release

You need to generate your own keystore and need to get Map keys for the same.
else you will not be able to see map on deployment of your apk onto the device.

Create a new keystore of your own and follow the same procedure for the generated keystore.
Its very easy to generate keystore also.
I simply export my android application via eclipse and it then do everything by itself.

Hope it helps :)

---

Related Topics