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 16406 [details]
Added the Facebook iOS SDK and I cannot compile and deploy to my device in debug. The error is
/work/rendr/audiograph/AudioGraph/iOS/MTOUCH: Error MT3001: Could not AOT the assembly '/work/rendr/audiograph/AudioGraph/iOS/obj/iPhone/Debug/build-iphone8.4-9.3.2/mtouch-cache/Build/Facebook.dll' (MT3001) (AudioGraph.iOS)
I'm seeing a discussion on the Forums about this issue, but didn't find any bug logged.
I've cleaned, rebooted, wiped bin/obj, rebuilt, etc.
Is there a workaround or solution?
Didn't know if this issue belonged here or elsewhere. Apologize if it's misplaced.
I could not reproduce that bug using a new iOS app project and adding the Facebook iOS SDK (v4.12.0) to it.
We'd need a test case to help track this down because the issue could have multiple causes, therefore we need to have the same binary and options as you.
Could you please link a test project to that bug?
I have ran into the same issue. More info: http://stackoverflow.com/questions/37955458/could-not-aot-the-assembly-facebook-dll-mt3001
I just installed updates today to see if I could send you a solution demonstrating this issue and the project runs. I also note that there was a release today of bug fixes as I compare my current environment with the environment from yesterday that had this issue for me.
I have also confirmed today's release seems to have fixed this issue in my client solution.
Current environment attached.
Created attachment 16433 [details]
I am still having the same problem with the latest build
And I was wrong, still getting the error when building for device. Sleep deprived, sorry.
I have a sample project that works fine, UNTIL I matched my build settings to my client project. Now I get the AOT error.
Created attachment 16441 [details]
Perhaps this would help, it's my build output.
No matter my build settings, I'm no longer able to get this solution to build for device. Repeatedly cleaning, building, deleting bin/obj....
These settings built successfully: https://www.dropbox.com/s/s47tbg3dzuufcqw/Screenshot%202016-06-22%2012.23.24.png?dl=0
I turned back on Incremental Builds and the AOT is back.
And confirmed these settings with Incremental Builds turned off works in my client project as well.
So what's up with the Incremental Builds option? Or is this coincidence that I can build/not build depending on changing that setting?
Although disabling Incremental Builds works great (thanks David!) this option helps to have a fastest deploy so disabling may affect capacity to test frequently on real devices.
I'd love to see a definitive solution without involving Incremental Builds
Thanks for the report!
*** This bug has been marked as a duplicate of bug 42139 ***