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 for Bug 23503 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 8260 [details]
Test Project from Customer
We have a report of an AOT compilation error (MT3001) when deploying to an iOS device using MvvmCross. I have tested using the attached sample application on an iPhone 5 running iOS 7.0 with both the current Stable and Alpha and has been able to reproduce. Test project is attached.
## Steps to reproduce
1. Open test project in Xamarin Studio
2. Run on a physical device and note compiler error
## Actual results
App does not compile and throws an MT3001 error indicating the inability to AOT the Autofac.Extras.MvvmCros.dll assembly. I have attached my verbose build log to this report.
## Expected results
App compiles without error.
## Additional information
The original reporter of the issue indicated the MT3001 error only shows when trying to run on device. I've gone ahead and tested in the simulator and noted a System.TypeLoadException:
Could not load type 'Autofac.Extras.MvvmCross.AutofacMvxIocProvider' from assembly 'Autofac.Extras.MvvmCross
## Version information
=== Xamarin Studio ===
Version 5.5 (build 222)
Installation UUID: ee07b9c8-41e3-496f-a1ab-e8a3ed3db20f
Mono 3.10.0 ((detached/53e3161)
GTK+ 2.24.23 (Raleigh theme)
Package version: 310000018
=== Apple Developer Tools ===
Xcode 6.0.1 (6528)
=== Xamarin.Mac ===
Version: 188.8.131.52 (Business Edition)
=== Xamarin.iOS ===
Version: 184.108.40.206 (Business Edition)
Build date: 2014-09-27 22:06:24-0400
=== Xamarin.Android ===
Version: 4.17.0 (Business Edition)
Android SDK: /Users/redacted/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.4 (API level 19)
4.4.87 (API level 20)
Java SDK: /usr
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
=== Build Information ===
Release ID: 505000222
Git revision: dae37674f8a41572a91bf0e14c098d15e03d0a53
Build date: 2014-09-26 14:15:04-04
Xamarin addins: bab982129fe7697d3c639fa713751ab29305a257
=== Operating System ===
Mac OS X 10.9.4
Darwin 13.3.0 Darwin Kernel Version 13.3.0
Tue Jun 3 21:27:35 PDT 2014
I think I've worked out where it's going wrong. The latest MVVMCross update added methods to the IOC interface which AutofacMvxIocProvider implements.
Now I'm not sure what is supposed to happen here. If AutofacMvxIocProvider is build against an older version of MvvmCross, shouldn't the compiler/linker complain?
The (managed) linker is not enabled, by default (it's "Link SDK"), on user* code. In fact the attached solution seems to build fine if you enabled "Link all assemblies".
That's very likely because the new, extra/missing, references are not used (and the linker removes them without having to even resolve them).
* i.e. on non-Xamarin code
@Zoltan can you validate the above ? (if the AOT compiler crash is related to missing symbols) If so how hard would it be to issue an error ?
The error handling code in the runtime is not complete, so sometimes missing references lead to errors like this.
That's odd because there are explicit references to the interface and the implementation. Why would the linker exclude them?