Xcode 4.6.2 app crashes on every second run

Question

Xcode 4.6.2 seems quite buggy.

When I run a second time my any project I get SIGABRT crash within the first second. I completely removed Xcode and reinstalled, (yeah I try turn off and on again). Also I removed command line tools and simulators, but that didn’t help either.

Goodbye

Have you tried adding an exception breakpoint as this one? – Face

I tried, but to no avail. It still crash on the main thread while attach process. – Goodbye

In AppCode all works great. I'll use it until the next update xcode. – Goodbye

Xcode 4.6.2 updated some compiler / architecture stuff (maybe it was 4.6)... make sure to clean your project (CMD+SHIFT+K) before building with the new Xcode update. – Guesswarp

Thanks, I know about clean. But it only help, if you clean every time before run. – Goodbye

did you find a solution by and chance? I am facing the same issue – Hazy

Yes, now I have found :) – Goodbye

Answer 1

ok, I found a solution. Please open the menu Product -> Scheme -> Edit Scheme, select Run YouAppName.app on the left, tab Info. Then choose GDB instead of LLDB in debugger field.

UPD: In new Xcode 4.6.3 this bug has been fixed. So just update your Xcode.

Goodbye

This was driving me nuts as well! I changed to GDB and it doesn't happen again. Wow. – Degauss

Just started getting this issue today, I thought it was a 10.8.4 thing (just updated), but changing to GDB worked for me too. What a crock. (Edit: actually, it may be just a 10.8.4 thing: tuaw.com/2013/06/05/devjuice-10-8-4-and-the-ios-simulator) – Dichlamydeous

Argh! Going back to a deprecated compiler, just to fix a (really painful) bug in the brand-new-state-of-the-art compiler is a big problem… But no choice, I'll have to do it. – Lifeless

Upvote for this as a solution, but are there any other options rather than switching to GDB? I was using the CMD., wait for 5 seconds but that got a bit boring – Voight

Answer 2

Found another way to fix this without moving the debugger to GDB. I usually just re-run an app by pressing ⌘-R while the app is running. Instead, kill the app from Xcode with ⌘-., wait 5 seconds and hit ⌘-R to run it. Counting the 5 seconds by saying "I love Xcode" seems to help too.

Edit: This issue is fixed in 4.6.3

Dichlamydeous

Also can use ⌘-. and ⌘+shift+K (without wait 5 second press) and then ⌘-R on every second run – Goodbye

I think the time it takes to clean the build is just doing the same thing, making you wait a few seconds. – Dichlamydeous

Yes, depending on on the size of project and the capacity of the computer. – Goodbye

Great, thanks! I found that "I love Xcode" wasn't long enough though, so I say "I'm in an abusive relationship with Xcode but I ain't gonna leave, I can change him" and that works just fine. – Dorindadorine

Answer 3

I suppose it has something to do with the latest update of iTunes (11.0.4), because I ran into the same issue after installing the update.

We might have to wait until Apple fixes this problem and go on with the above solutions which seem to work for me also.

Astaire

It's just started happening for me after installing iTunes 11.0.4 (and OS X 10.8.4), too. Oh Apple... – Dorindadorine

Me too! The app, when running in simulator, crashes every equal time. It works every unequal time. So it works first time, crashes second, works third, crashes fourth and so on... I have not tried device yet this time. I am using CoreData in the project if that makes any difference. But I am not using any other things, it's a very light test app with no real features yet, and the simulator just chokes like this... bad vibes. – Pinchhit