Bug 13154 - Display SHA1 fingerprint of the keystore that was used to sign an APK.
Summary: Display SHA1 fingerprint of the keystore that was used to sign an APK.
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.6.x
Hardware: PC Mac OS
: Low enhancement
Target Milestone: 5.1
Assignee: dean.ellis
URL:
Depends on:
Blocks:
 
Reported: 2013-07-10 14:05 UTC by Tom Opgenorth
Modified: 2015-02-20 16:16 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Tom Opgenorth 2013-07-10 14:05:01 UTC
Certain features such as Google Play require the SHA1 fingerprint of the keystore that was used to sign the application.  This SHA1 fingerprint is used in Google API Console to "whitelist" applications with some Google Services.

The current process requires uses to manually obtain the SHA1 fingerprint by opening up a command prompt/bash shell, and using the keytool utility from the JDK.

It would be handy if, as a part of building the APK, the build output displays the SHA1 fingerprint (and maybe even the path) of the keystore that was used to sign the application.
Comment 1 Jonathan Pryor 2013-07-11 14:10:10 UTC
The command is:

> $ keytool -V -list -keystore .../debug.keystore  -alias ALIAS -storepass STOREPASS -keypass KEYPASS

After discussion, just executing and printing the entire command contents would be sufficient.
Comment 2 Alexandre Rocha Lima e Marcondes 2015-02-03 07:28:50 UTC
I think it would be great to be able to choose the algorithm during the publishing process when using the JDK 7.
Comment 3 Alexandre Rocha Lima e Marcondes 2015-02-03 07:30:41 UTC
Just to give notice to Xamarin, there are duplicates of this report or at least somewhat related regarding the signing algorithm and JDK 7:

* https://bugzilla.xamarin.com/show_bug.cgi?id=24539
* https://bugzilla.xamarin.com/show_bug.cgi?id=23811
* https://bugzilla.xamarin.com/show_bug.cgi?id=22897
Comment 4 dean.ellis 2015-02-20 13:20:15 UTC
Fixed in monodroid/master/fe94c0a8