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.
Created attachment 3274 [details]
* Enable linking (either sdk only or all).
* Add this to a sample project:
Console.WriteLine (System.Diagnostics.Process.GetCurrentProcess ().MainModule.FileName);
* Run & watch it crash.
That's likely reflection-based without a corresponding rule (and never caught before since the API is not available in MonoTouch).
Native reflection this time:
Yup, the old audit (summer 2011) done on mono 2.10 code base did not cover code outside MT. I'll review the 3.0 code base keeping both MT and XM in mind.
Created attachment 3275 [details]
In the mean time a workaround is to use the --xml=file options to tell the linker to keep those types intact.
To do this
1. download the attachment and add it to your project
2. then go to:
Project Options, Build, Mac OSX Packaging > Advanced > Advanaced Mono Bundling Options > Extra Arguments
3. add the following (add the path to the file if needed)
Fixed in ad63829a65e50cb5ae862cc93e5bd453d58e1a98
It will be available in 1.0.64+