Re: Constantly Getting Assertion Failure
Re: Constantly Getting Assertion Failure
- Subject: Re: Constantly Getting Assertion Failure
- From: Don Quixote de la Mancha <email@hidden>
- Date: Fri, 11 Nov 2011 04:04:28 -0800
I once had some really screwy unexplainable problems happen to my
project when I had some spurious .svn (Subversion metadata)
directories in my source tree. That is, my tree was not under source
control, but I had copied an entire folder from a totally different
project that was under source control, without thinking to delete its
.svn directory.
To check for that, in the Terminal "cd" to the top of your source tree and then:
$ find . -name ".svn" -print
If it turns up any unexpected .svn directories, use "rm -r" or maybe
"rm -rf" to delete them.
Try it also for ".git" directories.
Of course this is not what you want to do if your project actually is
under source control.
I meant to write up a Radar bug about this but haven't gotten to it yet.
Another thing to try is to create a backup copy of your .xcodeproj
project file, then delete absolutely everything within the .xcodeproj
bundle directory other than the project.pbxproj file. Of course you
must quit Xcode before doing that.
If that doesn't fix your problem, again without Xcode running, open
your project.pbxproj file in some other text editor than Xcode. I use
Bare Bones Software's Text Wrangler for this.
Start by searching in the file for file or directory names that occur
in those spurious error messages. Delete all the entries that mention
any of them, while taking care to maintain the validity of the
project.pbxproj file format. You should not need to know the file
format in detail to be able to do that, it's generally obvious what is
safe to delete.
When you open your project in Xcode again, all the stuff you deleted
will be missing from your project. Use the Xcode GUI to add back in
any sources or headers you deleted, and check your project and target
build settings, then reconfigure them to be what you want.
It still happens to me all the time that my Xcode project bundles get
corrupted somehow. Sometimes that's my own fault, in that I
configured something incorrectly in the GUI, but I am only able to
figure out what is actually wrong by editing the project.pbxproj file.
But sometimes Xcode scrags the project file completely of its own
accord.
Finally, use the Terminal to examine the contents of every directory
in your source tree with the "ls -a" command. "-a" will show you all
the "Dot Files", that is, files that are normally hidden both in
Terminal and GUI views. "ls -asCF" will also show you the file type
with a symbol - "@" for symbolic links, "/" for directories and so on.
If you find any files that you think shouldn't be there, make a backup
of your whole source tree, then delete any spurious files from the
original.
If you *still* cannot fix the problem, again make sure you have a
backup of your whole source tree, then either delete your rename all
of your .xcodeproj bundles, then recreate them all from scratch. This
will go faster if you use the /Applications/Utiltiies/Grab.app program
to create screenshots of all your settings.
If it turns out that your problem really is project bundle corruption,
file a bug report at http://bugreport.apple.com/ and attach a
compressed archive of the bogus project, as well as any new project
you have created that corrects the error.
--
Don Quixote de la Mancha
Dulcinea Technologies Corporation
Software of Elegance and Beauty
http://www.dulcineatech.com
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden