Quando compilo la mia app con lo strumento da riga di comando xcodebuild
(XCode 4.2.1 - iOS SDK 5.0) casualmente lo ibtoold
(Interface Builder) si arresta in modo anomalo. Quando eseguo di nuovo la build, tutto funziona correttamente.XCode: Interface Builder si blocca durante la compilazione di XIB
il seguente errore accade:
ibtoold[88134:107] [MT] DVTAssertions: ASSERTION FAILURE in /SourceCache/IDEInterfaceBuilderCocoaTouch/IDEInterfaceBuilderCocoaTouch-933/IBPlugin/Utilities/IBObjectMarshalling.m:499
Details: Interface Builder encountered an error communicating with the iOS Simulator. If you choose to file a crash report or radar for this issue, please check Console.app for crash reports for "Interface Builder Cocoa Touch Tool" and include their content in your crash report.
Exception name: NSInvalidReceivePortException
Exception reason: connection went invalid while waiting for a reply because a mach port died
Exception backtrace:
(null)
Exception info:(null)
Object: <IBAssertionShim: 0x40047fac0>
Method: -reportMarshallingFailure:
Thread: <NSThread: 0x40010a220>{name = (null), num = 1}
Hints: None
Backtrace:
0 0x00000001068f42d4 -[DVTAssertionHandler handleFailureInMethod:object:fileName:lineNumber:messageFormat:arguments:] (in DVTFoundation)
1 0x00000001068f41a4 _DVTAssertionFailureHandler (in DVTFoundation)
2 0x00000001094f1e20 (in IDEInterfaceBuilderCocoaTouchIntegration)
3 0x0000000109572081 (in IDEInterfaceBuilderCocoaTouchIntegration)
4 0x00000001095720d4 (in IDEInterfaceBuilderCocoaTouchIntegration)
5 0x0000000106087d25 (in ibtoold)
6 0x0000000106085413 (in ibtoold)
7 0x0000000106085120 (in ibtoold)
8 0x000000010608502c (in ibtoold)
9 0x000000010608ed56 (in ibtoold)
10 0x0000000106084baa (in ibtoold)
11 0x0000000106085b8f (in ibtoold)
12 0x0000000106083644 (in ibtoold)
Command /Developer/usr/bin/ibtool failed with exit code 255
Qualsiasi idea di come risolvere questo problema?
Esattamente lo stesso succede a me. Hai trovato una soluzione? – Dmytro
Non ancora, è stato inserito un bug in Apple ... – x2on
Sembra che questo problema sia corretto in Xcode 4.3.1 per me ... – x2on