views:

158

answers:

6

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 SDK 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!

A: 

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.

TechZen
I currently have read and write permissions to the build folder.
OlivaresF
A: 

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.

Johan Kool
Yes, I've installed in developer. I basically formatted the drive because I installed an SSD and downloaded xCode from Apple.
OlivaresF
What's the path to the project? Any odd characters there?
Johan Kool
The path is:Users/anauel/Desktop/AP/TG/iOSTG so there are no spaces or unusual characters.
OlivaresF
A: 

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.

ergosys
Nope :(The path is:Users/anauel/Desktop/AP/TG/iOSTG so there are no spaces or unusual characters.
OlivaresF
+1  A: 

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

keno
I've checked and all those locations exist. The permissions seem to be okay. I've already just built the product using release as my configuration and it is working. It's just the build and archive feature that isn't.
OlivaresF
A: 

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

Marcus S. Zarra
Malcolmr just answered it. Thanks, though!
OlivaresF
+2  A: 

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.

Malcolmr
Yes! This actually works. I have absolutely no idea why! If I try it without "Generate Debug Symbols" it gives me the warning, but once it's on, it works flawlessly.Thank you!
OlivaresF
keno