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 for Bug 12515 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Calling AppDomain.CurrentDomain.GetAssemblies() in a second app domain in a release build doesn't return the list of assemblies.
See forum post for more information and a sample project that demonstrates the issue.
This is blocking for us because we are enable to upgrade Xamarin.Android beyond 4.6.00049. It definitely occurs in 4.6.06000, and a colleague of mine tried all versions after 4.6.00049.
I also confirmed that this bug exists in 4.6.08007
Is this bug going to be fixed any time soon, or should I implement a workaround?
Can you take a look at this one?
In case it wasn't obvious by now, we implemented a workaround ;)