Xcode 4: Build Failed, No Issues

Question

The app works fine in the simulator, builds and runs.

When I attach my device (iPhone 3GS running iOS 4.3) and target the iPhone, the result is \"Build failed\" with

Answer 1

see: http://developer.apple.com/library/ios/#DOCUMENTATION/FileManagement/Conceptual/understanding_utis/understand_utis_conc/understand_utis_conc.html

The UTI Character Set A uniform type identifier is a Unicode string that usually contains characters in the ASCII character set. However, only a subset of the ASCII characters are permitted. You may use the Roman alphabet in upper and lower case (A–Z, a–z), the digits 0 through 9, the dot (“.”), and the hyphen (“-”). This restriction is based on DNS name restrictions, set forth in RFC 1035.

Uniform type identifiers may also contain any of the Unicode characters greater than U+007F.

Important: Any illegal character appearing in a UTI string—for example, underscore ("_"), colon (":"), or space (" ")—will cause the string to be rejected as an invalid UTI. At the API layer, no error is generated for invalid UTIs.

Answer 2

I've been getting 'Build Failed' with no errors in the Issue navigator(only warnings). Report navigator, though, displayed errors correctly.

Answer 3

seems like there are many possible causes of this problem. Mine turned out to be that

My target was set to use a non-existent provisioning profile.

I set my project to use a new profile, and I deleted the old one. Didn't realize that the target had its own provisioning profile setting, which was still set to the old (now deleted) profile.

Answer 4

For me, the build failed without displaying any errors in the Issue Navigator. However, in the Log Navigator, in that build session, I could see the error. In my case, the error was an undeclared constant. I imported the required header file and the problem was resolved. I am not sure, why this error did not show up in the Issue Navigator.

I tried to reproduce this behavior by deliberately changing the name of another variable. This time, the error was displayed in Issue Navigator. So, I am still unsure about why wouldn't the earlier error show up in the Issue Navigator.

Hope this helps.

Answer 5

i clear all Spaces in project schemas in xcschemes and this resolve this issue. F***ing Apple :( AppCode ROCKS!

Answer 6

After going though all these answers, I had the exact same issue, but something different solved it for me.

The Problem:

Build failed without issues after refactoring. (Renamed a class using Edit -> Refactor -> Rename).

The Dumbest Solution Ever:

Go refactor (rename) something else (-_-"). After doing that, the error was that Xcode failed to rename all appropriate files, and didn't show errors. Then, after another refactor, the errors from the previous refactor appeared.