On May 1, 2007, at 11:42 AM, Greg Guerin wrote:
Hado Hein wrote:
After restarting the Finder I have a plain document icon which has no
associated app. Yes, I can choose Xcode to open it - but the project
doesn't get opened.
...
[snip stack trace]
The complete and utter failure to open the project suggests that the
unzipped project files are corrupted or malformed in some way.
To find out more, you'll probably have to examine or dissect individual
files in the .xcodeproj folder, using a hex editor of some kind, such as
Hex Fiend (google for it).
I'm not sure why you'd need a hex editor. Xcode project files are UTF-8.
Unless you are already familiar with the internal structure of a .xcodeproj
bundle, I recommend comparing the malfunctioning project against a
known-good project that Xcode can definitely open. If the corresponding
files don't exist or are radically different in structure (an XML file in
one case, a gzipped file in the other), that's probably the offending part.
The 'file' command may prove useful in identifying what kind of data each
file contains.
How to get uncorrupted originals out of a mangled or malformed zip file I
do not know.
It might help to go back to whatever data source you got them from and see
if they can be unzipped or validated there (assuming the zip checksums are
valid). Or find another copy of them somewhere.
A common cause of this is committing a project file that has SCM-introduced conflict markers into the repository.