On Jul 28, 2012, at 3:14 AM, Quincey Morris wrote: It seems to have been a source control issue. The local folder was missing, but svn thought it should still be there.
Still, a bit irritating that it seems to be a build issue.
IMO, SVN+Xcode is barely viable. Even if it costs you a few days of downtime, it's probably worth switching to git.
Not that git+Xcode is perfect. It's very good at managing the history of the contents of files, but it's not that great at managing the files themselves. There's not much that's more frustrating than Xcode shrugging its shoulders and saying, "Sorry, can't commit, you're on your own, buddy."
I think you hit the nail on the head. I'm super comfy with using the Versions app and SVN and confident with my ability on how to recover from errors in the SVN process.
So, knowing that issues will happen in check in/update, i can deal with those in Versions, but with all the fun we have when Xcode doesn't behave well, I really don't want to run in to yet another circumstance with Xcode shrugging its shoulders and saying "Sorry, can't commit, you're on your own, buddy." |