Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
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.
I think it would be great to be able to choose the algorithm during the publishing process when using the JDK 7.
Just to give notice to Xamarin, there are duplicates of this report or at least somewhat related regarding the signing algorithm and JDK 7:
Fixed in monodroid/master/fe94c0a8