Bug 415 - Reopening a xib while xcode is still running causes a crash
Summary: Reopening a xib while xcode is still running causes a crash
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-08-25 09:16 UTC by Alan McGovern
Modified: 2011-08-29 03:53 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 Alan McGovern 2011-08-25 09:16:13 UTC
1) Double click a xib in MonoDevelop to open in Xcode
2) Hit ctrl-w on the main window in Xcode to close it
3) Double click on the xib in MonoDevelop again
4) Xcode crashes

If we're re-opening the old xcode solution files when we do this maybe the fix i to create a new set of project files when we encounter this scenario.
Comment 1 Mikayla Hutchinson [MSFT] 2011-08-25 09:48:35 UTC
We do create new project files.
Comment 2 Mike Krüger 2011-08-29 03:53:25 UTC
Works for me, Which xcode version are you using ?

4.2 ? 

XCode is still beta, it's a bit crashy sometimes - mhutch is right, we create a new project file - I assume that this error is on xcode side.