Bug 34788 - Whenever I try to build for the simulator, it fails and gives me this error:
Summary: Whenever I try to build for the simulator, it fails and gives me this error:
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: XI 8.10
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-10-12 17:53 UTC by mario
Modified: 2016-06-09 13:52 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description mario 2015-10-12 17:53:06 UTC
/Users/marioandhika/mathchat-xamarin/MathChat/MTOUCH: Error MT5103: Failed to compile the file '/Users/marioandhika/mathchat-xamarin/MathChat/obj/iPhoneSimulator/Debug/mtouch-cache/main.i386.m'. Please file a bug report at http://bugzilla.xamarin.com (MT5103) (MathChat)

Xamarin Studio 5.9.7
Xcode 6.4
iOS SDK 8.4
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-10-13 05:53:24 UTC
Can you please attach the complete build log, as well as that file the error message mentions?
Comment 2 Sebastien Pouliot 2016-06-09 13:52:24 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!