Bug 17637 - Lots of error at open XCode
Summary: Lots of error at open XCode
Status: RESOLVED DUPLICATE of bug 10883
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Crash Reporter ()
Version: 4.2.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: master
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2014-02-06 10:05 UTC by diegodiazespinoza@gmail.com
Modified: 2014-02-06 10:34 UTC (History)
2 users (show)

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


Attachments
Exception thrown by Xamarin.Studio while open XCode (2.28 KB, application/octet-stream)
2014-02-06 10:05 UTC, diegodiazespinoza@gmail.com
Details


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:
Status:
RESOLVED DUPLICATE of bug 10883

Description diegodiazespinoza@gmail.com 2014-02-06 10:05:36 UTC
Created attachment 5990 [details]
Exception thrown by Xamarin.Studio while open XCode

Xamarin.Studio crashes often (but not always) at launching XCode. It throw the exception but not crashes completely (in fact XCode opens and Xamarin.Studio keep alive, just the exception). Attached the trace.
Comment 1 Alan McGovern 2014-02-06 10:13:21 UTC

*** This bug has been marked as a duplicate of bug 10883 ***
Comment 2 Alan McGovern 2014-02-06 10:15:29 UTC
I believe the fix for this issue has been shipped as part of Mono 3.2.7, so if you upgrade to that it should be fine.
Comment 3 diegodiazespinoza@gmail.com 2014-02-06 10:32:02 UTC
Mmmm, does really exist 3.2.7 for Mac OS? didnt find it anywhere....http://www.mono-project.com/Release_Notes_Mono_3.2#3.2.x_Series_Release_Notes
Comment 4 Alan McGovern 2014-02-06 10:34:53 UTC
My bad, it hasn't actually been released yet. It should be released soon, so just keep an eye on the updater for Mono 3.2.7 to become available