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 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.
I have a few suggestions/issues regarding building the production .apk
1) The menu option under the BUILD menu to package <appname> for android .apk is disabled. It took me a while to figure out how to build the .apk as it's under the tools menu now. It would be nice if the old menu item launched the same dialog
2) I have the signing info embedded in my .csproj to make repeated builds easier, that doesn't seem to be getting read in now and whenever I choose to build the .apk I have to enter all the info again
3) It would be nice if the signing info was remembered somehow whether in the dialog, .csproj, a .config file, something - I don't want to enter it every time I do a release build.
I noticed in the 4.6 release notes that if I have the NDK installed I can use native assemblies. Is this automatic or do I have to specify this option somewhere?
With regards to comment one, there are 2 separate menu items on for Packaging and one for Publishing. Packaging is just used to produce an .apk for ah-hoc distribution where are Publishing is used when producing .apk's for Google Play.
Both menu options are only be enabled for Release build.