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.
The linker is causing crashes on our project. This only happens on Android, with the proper LinkerPleaseInclude settings. iOS with the same settings causes problems.
It may be our configuration but it seems to work better or worse depending on the Xamarin studio version we have installed.
That should be causes no problems. It works flawlessly on iOS.
I have tried this issue but unable to reproduce this issue at my end.
If you get a chance, could you please attach Test sample application with a small testcase.
Also add IDE Log, Application Output and environment info.
You will find these details via:
1. IDE log: Help-> Open Log Directory.
2. Environment info: Help-> About-> Show Details-> Copy Information.
> This only happens on Android, with the proper LinkerPleaseInclude settings.
What are "LinkerPleaseInclude settings"?
Attached the cs file to hint to the linker. This builds on iOS.
It has problems in the core MonoDroid assemblies.
Created attachment 9415 [details]
What are your linker flags for the project: Link SDK Only or Full?
> It has problems in the core MonoDroid assemblies.
Which members are being linked away?
Would it be possible to get a full repro project?
Because we have not received a reply to our request for more information we are closing this issue. If you are still encountering this issue, please reopen the ticket with the requested information. Thanks!