Bug 6993 - Can't compile app using
Summary: Can't compile app using
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-09-07 11:45 UTC by Allie Miller
Modified: 2013-12-05 18:35 UTC (History)
2 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 Allie Miller 2012-09-07 11:45:59 UTC
Case #16430

When customer attempts a device build (either for debug or release/distribution), MonoDevelop inevitable crashes some time after starting 'Compiled to native code'. 

Crash report is here: http://pastebin.com/38G8x244

Can compile, debug and run on the simulator.

System info:
Mac Mini with 10.7.4
MonoTouch 5.2.13, then attempted 5.4 
MonoDevelop, then attempted using
Mono 2.10.9
XCode 4.3.1
Comment 1 Jeffrey Stedfast 2012-10-24 18:42:35 UTC
Hi Richard,

Could you attach the MonoDevelop log file from ~/Library/Logs/MonoDevelop-3.0/ from the particular session that crashes during your build?

They are tagged with the date & time that you started MonoDevelop.

Comment 2 PJ 2013-11-19 17:05:16 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:35:36 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.