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.
In Visual Studio 2012 the publishing system will use the values from the csproj file as outlined in http://docs.xamarin.com/guides/android/advanced_topics/build_process 2.12 to pickup the keystore alias and passwords. This does NOT work in Xamarin Studio. It would be nice if it would so I don't have to remember the information or enter it every time I want to build a package.
I think the VS addin is incorrect, those settings are intended for signing at build time, and the publish command is intended for re-signing built apks.
This is definitely a workflow that needs review, however.
This was fixed in 5.7. "Create Android Package" will use the csproj properties, "Publish Android Application" will still prompt for signing keys.