How to fix ibtool failed with exit code 255

Question

I have never encountered this problem before. The application used to run perfectly but now it always says this error. I have tried cleaning and rebooting. I have tried resetting IOS Simulator. I have tried deleting derived data.

This is what it says:

CompileStoryboard YoungstersTennisApp/Base.lproj/Main_iPhone.storyboard
cd /Users/DJ/Desktop/YoungstersTennisApp
setenv IBSC_MINIMUM_COMPATIBILITY_VERSION 6.0
setenv PATH "/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin"
setenv XCODE_DEVELOPER_USR_PATH /Applications/Xcode.app/Contents/Developer/usr/bin/..
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/ibtool --errors --warnings --notices --minimum-deployment-target 6.0 --output-format human-readable-text --compile /Users/DJ/Library/Developer/Xcode/DerivedData/YoungstersTennisApp-ftehnuqeslbyekfiszajlixujbqk/Build/Products/Debug-iphonesimulator/YoungstersTennisApp.app/Base.lproj/Main_iPhone.storyboardc /Users/DJ/Desktop/YoungstersTennisApp/YoungstersTennisApp/Base.lproj/Main_iPhone.storyboard

Command /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/ibtool failed with exit code 255

Any help for this would be great. I also have quite a large storyboard. Does that matter?

Thanks in advance!

Answer 1

I solved this in xcode 9 by unchecking and checking "Use Trait Variations" in storyboard File inspector.

xcode 🙃

Answer 2

On Xcode 9 getting error while building for archive: What worked for me was to clean my project, and then build for a simulator device, and then try to build for archive again. Xcode is rather temperamental sometimes...

Answer 3

I had this issue after with xcode 8.2 after deleting one of my view controllers. to fix it I just cleaned my build folder and it worked again

to clean build folder:

-> menu -> product (while pressing option) -> Clean build folder

or

option + shift + command + K

Answer 4

I also had this issue, after upgrade xCode to version 7.0 beta 6.

My way as below:

1. Delete the "DerivedData" folder

2. Rebuild the project (it will create new "DerivedData" folder )

Hope it will help to someone...

Answer 5

I also had this issue, after a big merge, and when i click on the .xib the xCode getting quit. Maybe you left some of the old Code, check the id of the view, also the id with problem is shown in the detail screen of the error message when xcode Quit so:

• Open the .xib with the text editor
• Check that the id of an element should appears twice; in the "subviews" group and in "connections" group if you connected as a property
• remove the the code that you don't need and save the file

Hope it will help, Constantin

Answer 6

I had the same issue with XCode 6 and iOS 8.

Just a XIB was giving me errors when I tried to compile.

I've tried to clean the project and the problem persisted.

Then I've opened the view that was giving me problems, I've saved again (WITHOUT CHANGING ANYTHING AT ALL) and... voila! My app up and running. XCode is satanic :)

Answer 7

Cleaning project, cleaning build folder and restarting xcode solved the issue for me.

Answer 8

I got the same error I could not find exact solution for that. After some time I realised my problem. My project files are AppDelegate.h

AppDelegate.m

LoginViewcontroller.h

LoginViewXontroller.m

LoginViewController.xib

I have added one new storyboard file. And I changed label and button connections from nib(.xib) file to storyboard file. After that I got this error.

I removed connections from storyboard and added connections to .xib file again. clean and build that's it my problem is solved. I hope it will helpful to someone..

Answer 9

Cleaning ang re-building project solved the problem for me (xcode 5)

Shift - cmd - K 
cmd - K

Answer 10

I ended up with this issue by having a UITableView with static cells that wasn't in a UITableViewController, but instead had a subclass of a UIViewController. Changing my subclass to instead inherit from UITableViewController fixed the problem.