JDK 7 changes keytool output

Question

I am using keytool JDK to create a Google Maps API key fingerprint. Although I declined several times, I realized that I had recently upgraded the JDK to 1.7. So I switch my directory to JDK6 (Thank God the old version remains.) And I repeated the same command:

D:\.android>"C:\Program Files\Java\jre6\bin\keytool" -list -alias androiddebugkey -keystore debug.keystore -storepass android -keypass android

and bang! It works. It turned out that JDK7 generated the SHA1 fingerprint instead of MD5, which leads to the rejection of my submission to Google. Therefore, I wonder why this happens for the new version of the JDK. Does anyone have any clues?

Answer 1

keytool -keyalg, . , , .

, - Oracle.

Answer 2

keytool.exe -v , MD5 ..

exampl: C: [jedk path]\bin\keytool.exe "-v -list -keystore" C:\Document s Settings\Administrator.android\debug.keystore "

Answer 3

-digestalg SHA1 -sigalg MD5withRSA jarsigner.

Answer 4

:

With JDK 1.7, I had problems with authorization. I finally figured out how to create the right debug repository using SHA1. Here is the command I used:

keytool -genkey -v -keyalg RSA -sigalg SHA1withRSA -keystore "%USERPROFILE%\.android\debug.keystore" -storepass android -alias androiddebugkey -keypass android -dname "CN=Android Debug,O=Android,C=US"

After creating it, you can see it with the command:

keytool -list -v -keystore "%USERPROFILE%\.android\debug.keystore" -alias androiddebugkey -storepass android -keypass android

The Signature algorithm should now read "SHA1withRSA." Copy the SHA1 fingerprint and paste it into the Google Key "Android Application Key", and you should be good to go.