Currently Being ModeratedJul 15, 2011 9:14 AM (in response to kathyfromsan francisco)
Handled. Would like to figure out how to delete posts.
Currently Being ModeratedJul 15, 2011 10:39 AM (in response to kathyfromsan francisco)
If you are a level 2 or above, you can report posts, including your own. Generally, the hosts don't like to delete things unless there are actual abuse or privacy issues. It would be better to just reply with what you did to fix your problem so that when someone finds a similar problem in the future, they can find this posting and get a hint about how to fix it.
Currently Being ModeratedJul 16, 2011 10:33 AM (in response to kathyfromsan francisco)
Reply to yourself, explain whatever the solution was and mark it as the solved / correct answer if you like. Otherwise, the thread is left as-is and occupies Apple's bit-space for a long time.....
Currently Being ModeratedOct 25, 2011 8:05 AM (in response to kathyfromsan francisco)
If you have time, can you post how it was "handled"?
Currently Being ModeratedNov 11, 2011 4:11 AM (in response to kathyfromsan francisco)
Experiencing the same error but only on certain build machines. Does anyone know what the cause of the ibtool 255 error is? Thanks
Currently Being ModeratedDec 14, 2011 9:25 PM (in response to kathyfromsan francisco)
Unbelievably frustrating that you've not indicated how you solved your own problem. Pretty much the worst thing you can do...
Currently Being ModeratedDec 15, 2011 9:09 PM (in response to kathyfromsan francisco)
Anyone found the fix yet? I have the same problem.
Currently Being ModeratedDec 16, 2011 7:39 AM (in response to kathyfromsan francisco)
Had the same problem today and instantly googled to find a solution - actually I only clicked "Run" another time and it worked again (as suggested here: http://stackoverflow.com/questions/6752961/command-developer-usr-bin-ibtool-fail ed-with-exit-code-10).
Currently Being ModeratedJun 12, 2012 7:38 PM (in response to kathyfromsan francisco)
Why don't you post what the solution was? Isn't that the obvious thing to do?
Currently Being ModeratedSep 13, 2012 8:27 PM (in response to kathyfromsan francisco)
I had this issue. I tried opening the file in interface builder and it crashed the entire IDE. I rolled back the file, and reimplented the changes, and everthing was fixed.
Currently Being ModeratedDec 10, 2012 1:36 AM (in response to kathyfromsan francisco)
Argh. never just write "Handled.". It is frustrating that you leave out the solution to the problem.
I'm having just this problem now.
ibtool failed with exit code 255
Currently Being ModeratedDec 15, 2012 11:32 AM (in response to Codepool)
This is a different issue. Exit code 10, not 255.
Currently Being ModeratedMar 28, 2013 5:28 PM (in response to kathyfromsan francisco)
I had a similar issue (where ibtool failed with exit code 255). Nothing suggested here worked for me.
Here is what I did and observed:
* The simulator started acting really weird - and became unusable (as in spinning beach ball unusable)
* Force quitting the simulator and restart it did not help.
* Closing Xcode and restarting it did not help.
* rebooting my maching did help *BUT* before it started, it prompted me to re-install the Simulators (6.1) which were already installed.
Now my app compiles and runs on the simulator.
Currently Being ModeratedSep 27, 2013 11:47 PM (in response to kathyfromsan francisco)
I've solved the issue, but it required a hard reset.
Some said it was because I installed XCode outside of the App Store, or because the simluator was buggy, or because XCode was pointing at the wrong version of the Simulator, or a resoruce was missing a target membership, or whatever. I tried all of that.
I downloaded XCode from the App Store, re-installed the Simulators, and still no luck. So I just rolled back my repository to an earlier date, and lost some work in the process. Not much though, because I always commit little and often.
Since ever starting to use storyboards back in 2011, I have always committed little AND OFTEN. Storyboard are fragile.