Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Interface Builder assertion failure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Interface Builder assertion failure

Subject: Interface Builder assertion failure
From: Hauke Klein <email@hidden>
Date: Wed, 2 Apr 2008 11:09:22 +0200

Hello, I'm having some problems with assertion failure alerts when using IB 3.0 (with Xcode 3.0 on Mac OS 10.5.2). The problem occurs in an Xcode project with two targets. One of them is an external target building a version of the Ghostscript framework and the other one is a regular Cocoa application.

As usual, the Cocoa application has an associated NIB file. Opening this file in IB produces one or more assertion failure dialogs with error message "Resources must have a value!". The NIB file itself is still the original application template file, so it should not be the cause of any problems.

I found an earlier thread describing a similar problem. In this tread, the problem was caused by files in the Xcode project using an image file extension which were not actually image files. Removing the references to all .ps files contained in ghostscript almost solves my problem. Now, I'm just having a single assertion failure (before removing the references I had about 10 cascaded messages). The backtrace of this remaining assertion failure starts with

Backtrace: 1. Interface Builder 0x00006a9a [IBApplication handleAssertion:inFile:onLine:] 2. CocoaPlugin 0x00b02dfd [IBCocoaDocument synchronizedFileExtensions] 3. CocoaPlugin 0x00b031aa [IBCocoaDocument willSynchronizeWithProjectFiles:project:] 4. InterfaceBuilderKit 0x002409cd [IBDocument beginSyncingWithXcodeIfNeeded] 5. Foundation 0x9392dfce [NSRunLoop runMode:beforeDate:]

There is no mention of synchronizeMediaWithModifiedProjectFiles:project:status: anymore. But the problem still seems to be caused by a file in the ghostscript source tree. When removing the reference to the entire ghostscript directory, I can open the NIB with no problems, and the assertion failures reappear after adding the ghostscript directory.

Does anybody knows what other file types might confuse the Interface Builder when synchronizing with Xcode? Of course, I might split the project in two separate projects, but I would prefer to avoid this. _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden Prev by Date: [ADMIN] Monthly Reminder: How to Ask for Help on Xcode-users Next by Date: Re: How do you build a dependency with a different configuration Previous by thread: [ADMIN] Monthly Reminder: How to Ask for Help on Xcode-users Next by thread: export PowerPlant CW9 project into xcode Index(es): Date Thread