Bug 494 - Cannot edit XIBs dues to Xcode assertion
Summary: Cannot edit XIBs dues to Xcode assertion
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.8 Alpha 2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-08-28 08:15 UTC by René Ruppert
Modified: 2011-08-29 08:06 UTC (History)
6 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 René Ruppert 2011-08-28 08:15:49 UTC
I upgraded my project to MD 2.8 Alpha 2.
Platform is Lion with Xcode 4.1 and MT 4.0.6.

When I double click a XIB, Xcode 4 comes up but fails with this assertion:

ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilder/IDEInterfaceBuilder-1617/Framework/Utilities/IBFoundationAdditions.m:1916
Details:  Both arguments are required
Function: NSString *IBRelativePath(NSString *, NSString *)
Thread:   <NSThread: 0x401f21180>{name = (null), num = 7}
Hints:   None
  0  0x0000000107f7c152 -[IDEAssertionHandler handleFailureInFunction:fileName:lineNumber:messageFormat:arguments:] (in IDEKit)
  1  0x00000001076171bc _DVTAssertionHandler (in DVTFoundation)
  2  0x0000000107627304 _DVTAssertionFailureHandler (in DVTFoundation)
  3  0x000000010aa584f3 IBRelativePath (in IDEInterfaceBuilderKit)
  4  0x000000010ab788e4 +[IBClassDescriptionSource(InstantiationConvenience) workspaceDocumentSourceIdentifierForInterfaceFile:inWorkspaceDocument:] (in IDEInterfaceBuilderKit)
  5  0x000000010ab7d2d8 -[IBClassDescriptionBasedClassProvider integratePartialDescriptionsFromFiles:inWorkspaceDocument:errorsPerFile:] (in IDEInterfaceBuilderKit)
  6  0x00000001075c57f9 __38-[DVTDispatchLock performLockedBlock:]_block_invoke_0 (in DVTFoundation)
  7  0x00007fff8f775afd _dispatch_barrier_sync_f_invoke (in libdispatch.dylib)
  8  0x00000001075c57a9 -[DVTDispatchLock performLockedBlock:] (in DVTFoundation)
  9  0x000000010ab8968b -[IBHeaderScanningClassProvider performBlockEnsuringNotCanceled:] (in IDEInterfaceBuilderKit)
 10  0x000000010ab8a853 __block_global_4 (in IDEInterfaceBuilderKit)
 11  0x00007fff8f77390a _dispatch_call_block_and_release (in libdispatch.dylib)
 12  0x00007fff8f77515a _dispatch_queue_drain (in libdispatch.dylib)
 13  0x00007fff8f774fb6 _dispatch_queue_invoke (in libdispatch.dylib)
 14  0x00007fff8f7747b0 _dispatch_worker_thread2 (in libdispatch.dylib)
 15  0x00007fff87a373da _pthread_wqthread (in libsystem_c.dylib)
 16  0x00007fff87a38b85 start_wqthread (in libsystem_c.dylib)
Comment 1 Sebastien Pouliot 2011-08-28 10:30:54 UTC
-> monodevelop
Comment 2 Mikayla Hutchinson [MSFT] 2011-08-28 14:56:44 UTC
This is an Xcode bug, but maybe we can work around it.
Comment 3 René Ruppert 2011-08-29 03:53:21 UTC
A small update: updating to Xcode 4.2 Beta 6 does not fix it.
Comment 4 Alan McGovern 2011-08-29 05:31:40 UTC
I'm running that version of xcode and do not have this issue. Would it be possible to attach the solution, or a reduced version of the solution, so I can replicate the issue locally?
Comment 5 René Ruppert 2011-08-29 05:35:09 UTC
I doesn't really matter. I can use any solution, even new ones. Always the same issue. Are you running it on Lion or Snow Leopard?
If it is not reproducible, I will reinstall my Macbook and give that a try.
Comment 6 Alan McGovern 2011-08-29 05:38:30 UTC
Strange, I have the same setup except a newer MonoTouch. The MonoTouch version doesn't affect this code though. Which template are you choosing when you're creating a brand new project? Maybe there's something in the autogenerated code that Xcode doesn't like.
Comment 7 René Ruppert 2011-08-29 05:43:21 UTC
One was iPhone/iPad universal, the other one was a blank iPhone project where I added the XIB manually.

But I have just done a small test here on my work Mac and it is not giving the assertion here. So it might really be an issue specific to my Macbook.

Stop worrying about it for now, I'd say. I will reinstall and report the bug again if the problem is consistent.

Or do you have an idea how to fix it without reinstallation?
Comment 8 Alan McGovern 2011-08-29 06:09:52 UTC
My only suggestion would be to remove everything to do with xcode and then reinstall it. It looks suspiciously like an xcode only issue, but I've no idea what might cause it for you and not us. No-one else has come across this particular crash.

The stacktrace provided implies the bug is in Xcodes header parser which means everyone should crash equally as we all use the same generated files. It just doesn't make sense.
Comment 9 Mike Krüger 2011-08-29 08:06:27 UTC
Ok closing as works for me. Reopen if it happens again after the reinstallation.

(Yes looks like an xcode issue, xcode could've much better error messages IMO)