Subscribe to
NSLog(); Header Image

Xcode Stability


13 Responses to "Xcode Stability"

  1. At least three times daily.

  2. Uh oh... Did you loose any PF changes?

  3. Yea, I see this at least a couple of times a day as well.

  4. I don't understand: "The application Xcode has expectedly quit"

  5. The dialog is just trying to be honest.

  6. Every once in a while, I go and edit the strings in /System/Library/CoreServices/, so that that dialog is more entertaining. Thinks like:

    "The application %@ has expectedly quit."

    "The application %@ has quit, deal with it."

    "I bet you were wondering why you don't see %@ anymore."

    "%@ got tired, and went home."

  7. Hi, I was just reading your blog and I think it has good potential. Would it be possible to blog roll me or add a link to my site please? My url is

  8. Yeah, happens to me quite a bit too.

    It's the most unstable application I use regularly which is pretty sad; you think they'd be able to get their own IDE right

  9. In addition to the memory leaks, general slowdowns, and a sundry of other problems with XCode, losing data from a crash just sucks. Save like you vote: early and often.

  10. At least Xcode saves your project state. It's damned annoying when Safari does this when you have three open windows with twenty tabs.

  11. xCode doesn't crash on me too often, but what drives me up the wall is when I'm re-factoring a source tree ( consolidating, breaking things up, moving files from one branch to another, etc ) and xCode won't build unless I shut it down and restart it. It "loses" the files.

    But, on the other hand, I love it anyway. It just feels better to me than PB ever did.

  12. Press "Submit Report..." and it might just get fixed. (And I'm not being cynical, either.)

  13. I think Apple is aware of these problems (even thought I did not encounter it yet), there is a QA job just for the development tools right now on