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.
When you upload an app created with the default Debug configuration to TestFlight, the app doesn't function correctly.
Steps to reproduce:
1) Create a new Android Application template
2) Choose Project->Publish to TestFlight
3) Enter tokens, notes, and distribution list(s)
4) Press OK
At this point, it shows you the package creation dialog, which says the shared runtime will be included in the package. http://screencast.com/t/4p9romdBL
Presumably this is an attempt to have this configuration work, but I'm not sure.
5) Press OK
6) App uploads to TestFlight
7) User installs/opens the app on their device
App should work (for template app, button should appear and respond to clicks with a label update), or I should be warned before uploading that my configuration is invalid.
App does not work, the button does not appear etc.
Note: The same app works fine when de-selecting the shared runtime option.
Setting to enhancement.
TestFlight no longer supports Android.