I just solved a problem that had me up until 2am last night and wasted about two more hours tonight. Hopefully this will help someone else spend a little less time on this issue should they encounter it.
I had just finished my newest iPhone app and was ready to submit it to the App Store. I used the “Build and Archive” option in the build menu of Xcode (as I had several times before), brought up Organizer and clicked “Validate Application…”. It prompted me to select my application and provisioning profile. I clicked OK.
Waiting…
Waiting…
Waiting…
Nothing! No message. No firewall activity. Nothing at all.
Googling. Googling. Googling some more. Came across a few things, but nothing solved my problem.
I had read somewhere a few days ago about Apple logging things that happen in Xcode to the system logs without telling you about it in Xcode, leading to mysteries like the one I had on my hands. So I opened up Console.app (/Applications/Utilities/Console.app) and started poking around.
What I found was this:
This told me a few things:
- That the IPA creation had failed.
- The command that Xcode was trying to run when I built my app.
- The error message that occurred when the command ran.
To make a long story short, in an effort to preserve the ability to test older OS versions in the simulator, I had installed the latest version of Xcode in an alternate location from the usual “/Developer” path that it defaults to. I do this (as many other iOS devs do) because even though Apple allows you to set your deployment target to something less than the current version, they like to remove all of the older SDKs every time they release a new version of Xcode. Turns out, I had put a space in the folder name.
In case you’re wondering, I’m still not sure why I ended up using ‘Developer 4′ as a folder name for Xcode 3.2.3, but that’s neither here nor there. My guess is that it was another of those 2am coding sessions. 
Comments
Leave a Reply