Bug 2447 - Key Store verification fails when publishing android application
Summary: Key Store verification fails when publishing android application
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.0
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-12-09 22:23 UTC by John Moore
Modified: 2014-07-30 07:39 UTC (History)
4 users (show)

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:

Description John Moore 2011-12-09 22:23:48 UTC
signing android apk files through monodevelop (Project -> Publish Android Application) is failing to accept my existing keystore.  No key store information has been added to the csproj file.  After selecting the key store, entering the password, alias and key password, md displays the following error message "Keystore verification failed:"  After receiving this error i manually signed a fresh apk file from the projects bin directory and was able to upload it to the android market and activate the updated apk, that indicates to me that the key store is not currupt and i have not lost the passwords.
Comment 1 John Moore 2012-04-07 19:11:16 UTC
issue is resolved for me in m4a 4.0.6/ plug in version