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.
Further to the error, I am getting the error pop up of "File not found: /MTOUCH"
`MT3001` errors means to AOT compiler could not complete it’s job. Without a full build log (one done with `-v -v -v -v) it’s not possible to guess why it happened, nor to suggest potential workaround.
The best way to get this resolved is to attach the assembly that resulted in the `MT3001` error. Ideally a full, self-contained test case is much better. Also having all the versions* information is required.
`*` The easiest way to get exact version information is to use the "Xamarin Studio" menu, "About Xamarin Studio" item, "Show Details" button and copy/paste the version informations (you can use the "Copy Information" button).
The recent MT3001 errors comes from additional checks done by the AOT compiler .
That spotted a bug in the linker where an assembly could be invalid (e.g. peverify would not be happy) but that did not affect most application (it never was reported before).
However that new check nows prevent a successful build. As such it's being, temporarily, disabled for 8.10.2.x. You can download it from , it's identical to the beta being released today - but it also removes the check.
 the check is new in XI 8.10.1.x, going back to 8.10.0.x should be fine (or the issue is different) using https://kb.xamarin.com/customer/portal/articles/1699777-how-do-i-downgrade-to-an-older-version
Beside the workaround in the 8.10 service releases the root cause is also fixed in XI 8.99 previews.