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.
Seems like the AndroidLinkSkip feature is not working. I'm trying to prevent an assembly from being linked to work around bug 29900 in the platform. However, the assembly is still linked which results in me having to turn off linking for all assemblies to get a Release build out. Our apk unfortunately goes from 18MB to 43MB which is unacceptable. Other users seem to [have reported](http://forums.xamarin.com/discussion/16279/android-skip-linking-broken-in-4-12-03003) the issue as well.
Thanks for the report.
If you have "Project Properties -> Android Options -> Linker [tab] -> Linking" set to "Sdk Assemblies Only", then the _application assembly_ isn't being _modified_ by the linker anyway.
The problem with Bug 29900 is that the linker is _reflecting_ on the application assembly to determine which types are safe to link out of the _other_ (SDK) assemblies. So unfortunately, if the linker is enabled _at all_ then you will hit Bug 29900, regardless of how many assemblies you skip using the `AndroidLinkSkip` property.
In short, I believe this bug can be marked RESOLVED ANSWERED (or similar).
Yes, that's right. Even when the assembly is marked to be skipped, it needs to be loaded. Fortunately the bug #29900 is already fixed.
I'm still seeing this behaviour with Xamarin.Android 220.127.116.11 and Xamarin 3.11.666.0.
After further research, the problem I'm seeing is that XamarinVS and Xamarin Studio maintain different lists of skipped assemblies and the one that was in Visual Studio was the correct list but the one shown in Xamarin Studio was wrong (and the linker uses the XS version). So I fixed the list in Xamarin Studio and now it links correctly.
To be honest, it might have been a bad merge...