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.
1) Compile binding dll.
2) Compile sample solution.
3) Deploy and run solution on device - it works
4) make clean dll
5) make dll
6) Deploy and run solution on device - it crashes
1. The workaround is just to force the dll to be rebuilt, in which case the mdb will be overwritten too.
2. & 3. Forgotten ;-)
The problem occurs when resources for a binding library has been modified, but the managed code is identical.
This (without the workaround) results in the AOT compiler re-compiling the assembly, but we don't update the dll in the app bundle because it hasn't changed, thus creating a GUID mismatch between the dll and the AOT'ed code.