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 14750 [details]
Project with report case. Just click the button on x86 device.
We had many crashes reported in our app after upgrading to 6.0 version.
System.TypeLoadException: MVAR 1 (TResponse) cannot be expanded in this context with 1 instantiations assembly:<no_image> type:<unknown type> member:<none>
All crashes were only on x86 devices.
Repro project is in attachment. Launch it and click the button.
It always crashes on x86 device (tested GT-p5200 , Galaxy Tab 3) and works good on ARM device (tested Nexus 7).
The code contains some combination of generic functional wrappers, async calls and indirect type instantiations.
After extracting it all out of our infrastructure, exception changed from TypeLoadException to NullReferenceException for some reason.
I'm able to reproduce this on an Asus ZenPad 7.0(x86) running Android 5.0.2:
logcat output: https://gist.github.com/pjcollins/c1f5fd60cf950ec798e9
We have the same issue
On android x86 devices and on iOs simulator https://forums.xamarin.com/discussion/61715/only-ios-simulator-crash-device-works-fine
Do you have ideas how it can be resolved?
I was unable to reproduce this bug with the current monodroid/master, commit 1832905a5510314f6d259f3f0c3186451ae04ceb
Tested on Dell Venue as well as in a couple of x86 emulators.
Please test with either the latest Xamarin.Android stable release or the current beta and reopen the report if the issue still happens for you.