Xcode's Build and Archive not working

The current issue I'm having is that Build and Archive will build my current target but after it's finished building, a pop-up will appear with the message:

"The operation couldn't be completed. No such file or directory"

I have reinstalled Xcode (3.2.3 with S开发者_如何学JAVADK 4.0), rebooted my machine, cleaned the cache, cleaned the project, manually deleted the project build directory. Nothing has worked.

I've also checked ~/Library/MobileDevice/Archived Applications and it is empty.

Any ideas?

p.s. This is driving me crazy!

The error The operation couldn't be completed. No such file or directory also occurs in XCode 4.0 GM preview if you do not change identity to "Don't Re-sign" after selecting (Archives) Share in the Organizer

I had this problem and the solution that was recommended to me was:

1. Open your Xcode project
2. Select Unity-iPhone in targets (Double click so it opens the info)
3. Find "Generate Debug Symbols" and check it on. (Just Search for it in the search field)

This worked for me, but I still don't understand why it was necessary.

All answers failed. Best solution, drag the .app bundle to iTunes and reveal the app in Finder. Boom! you get your ipa there.

Since it only seems to happen with your release configuration, double check the "Build Locations" values in your project settings for the release configuration.

• Check the paths in the "build locations" to make sure they exist
• Check the permissions for those paths
• Try doing just a build (no archiving) for your release configuration

Also keep an eye on your build results window during the build to see if there were any warnings during the signing and packaging stages that could give you clues

Had the same issue and none of the mentions solutions worked. I finally found the problem when I tried to directly sign the app with the adhoc profile: it told me that I had twice a distribution profile in my keychain. I deleted the old one, then compiled again with the dev profile, and then archiving with the adhoc profile and it worked.

Longshot answer - do you have any unusual characters in your project path? This release note indicates it can cause problems:

While most known cases have been taken care of, having a space, comma, slash, backslash, tilde, or other character special to the Unix shell in the directory name of any parent folder of your project can cause your project build to fail in unexpected ways.

If you have a 3:rd party SDK you need to add "$(SDKROOT)/ResourceRules.plist" to the “Code Signing Resource Rules Path” key in the targets build settings.

I solved this problem by exchanging the wildcard adhoc distribution profile I was using for an app specific adhoc distribution profile.

Of the top of my head, I would check permissions. Some code reports permissions problems as there being no file/folder. Check the Console log. You will sometimes find more info there.

Did you install into /Developer? If you've customized that folder the issue could be that the path contains a space, which could be causing your problem.

Run the Console app and see what information is being spit out there. That should give us more insight into the issue.