How to fix “failed codesign verification” of an iPhone project?

Question

Last night, the iPhone project was built perfectly.

This morning, I installed XCode 3.2.3 in a separate folder. When I open the same project in

Answer 1

The parallel XCode problem can be addressed using the command line tool "xcode-select"

I found a similar problem caused by having XCode 4.2 beta installed. One of the embedded entitlements files was being placed in a different directory and was causing a file not found error.

The solution was to use xcode-select to verify and fix the XCode path.

Answer 2

I'm not sure, but reverting those changes in the project.pbxproj rescues me from failing to start my app in devices. The warning subject of the question remain though.

@@ -325,6 +325,7 @@
                                PREBINDING = NO;
+                               "PROVISIONING_PROFILE[sdk=iphoneos*]" = "";
                                SDKROOT = iphoneos;
@@ -361,6 +362,7 @@
                                PREBINDING = NO;
+                               "PROVISIONING_PROFILE[sdk=iphoneos*]" = "";
                                SDKROOT = iphoneos;

Answer 3

Simple Solution: Build your app using a DISTRIBUTION certificate and not a Developer cert.

Answer 4

If you go to the Organizer and select Provisioning Profiles, is the profile listed there? If so, have you checked that it's setting in the Project Settings/Build/Code Signing section?

Answer 5

Besides googling for possible solutions to this problem and trying them out (hoping that they help), here is an advice how to diagnose what causes this. The steps below apply to Xcode 4.2.

1. In menu, select View > Navigators > Show Log Navigator. The Log Navigator should be displayed on the left side.
2. In the list of builds, select the one that causes troubles. The log from the build will be shown in the main view.
3. Scroll to the very bottom. The last two steps should be CodeSign and Validate, where the Validate step contains the warning.
4. Expand CodeSign and inspect the parameters used to perform the code signing.
5. Expand Validate to learn more about the errors/warnings.

Also scroll up and inspect the heading for the build target:

Build Target (your build target)

Project (your project) | Configuration (selected configuration) | Destination ...

In my case, I found out that while doing the Archive build, the app was signed with the developer certificate. Inspecting the heading for the build target revealed that the Release configuration was used to build the archive. The remedy was to:

1. In the menu, select Product > Edit Scheme
2. In the Edit Scheme dialog, select the Archive build item (list on the left)
3. Change Build Configuration to Distribution

I had this issue after duplicating a build target. The original target was signed by the distribution certificate. However, when copying the target, Xcode decided to assign the Release configuration to the Archive build.

Answer 6

This is kind of an old post but I wanted to share what I learned (really remembered because I forgot this part.) I was trying to build my project against an ad-hock profile. I had forgotten that I needed to create a separate App Store profile (Provisioning Portal -> Provisioning -> Distribution). This was my first app I've submitted and the documentation is overwhelming so I missed/forgot about this part. Once I created the App Store profile and installed in XCode everything worked fine. Just wanted to throw this out there in case anyone else has this same issue.