Application failed codesign verification. What do

问题:

XCode gives me this warning when I build the app for release.

Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)

Do I need to delete all entries from my keychain and redo getting a certificate, provisioning profile, etc?

I can build and debug on the iPhone and iPad without a problem.

If you know how I can solve this dilemma, please provide exact steps or a way for me to contact you about this.

Thanks

----UPDATE -----

Build Log

Validate build/Release-iphoneos/iApp.app cd "/Users/iosdeveloper/Documents/Programming/iPad/iApp HD" setenv PATH "/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Developer/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin" setenv PRODUCT_TYPE com.apple.product-type.application /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/Validation "/Users/iosdeveloper/Documents/Programming/iPad/iApp HD/build/Release-iphoneos/iApp.app"

warning: Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011) Executable=/Users/iosdeveloper/Documents/Programming/iPad/iApp HD/build/Release-iphoneos/iApp.app/iApp codesign_wrapper-0.7.10: using Apple CA for profile evaluation /Users/iosdeveloper/Documents/Programming/iPad/iApp HD/build/Release-iphoneos/iApp.app: valid on disk /Users/iosdeveloper/Documents/Programming/iPad/iApp HD/build/Release-iphoneos/iApp.app: satisfies its Designated Requirement test-requirement: failed to satisfy code requirement(s) codesign_wrapper-0.7.10: failed to execute codesign(1) - (null)

回答1:

You probably need to check what code signing profile is selected in your distribution build properties.

回答2:

Here's the checklist I go through when I've hit this:

1. Clean all targets, exit Xcode, then go drag the build folder from your project to the trash.

2. Do the Get Info on your project, make sure the Code Signing Entitlements and Code Signing Identity are selected correctly. Do the same for your Targets.

3. Login to the iOS Provisioning Portal and make sure the Distribution certificate has not expired. Also check the Distribution Provisioning Profile and make sure it is Active. Make sure the Certificate is properly in your Keychain and the Distribution profile is in Xcode Organizer (if you have multiple of the same one, delete all but the correct one and redo step #2).

4. Look at your Build Results on the failure and identify which profile it is actually using and make sure it is the right one.

回答3:

It looks like your target is "Development" but Xcode applied some of distribution settings to it, so the warning simply means your ad-hoc build has no valid AppStore submission certificate. Go to your target settings, choose the Release configuration and uncheck "Validate Built Product" option.

回答4:

Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011) i am got the Same Warning Message...

I just Changed to iOs Deployment target 4.3 to 3.2.2 its works perfectly .....

回答5:

Note: you may have to go to XCode's "Project" and select "Edit Active Target (appname)", which is near the bottom of the list ... in the new pane that opens, select "Build", then under "Code Signing Identity" select your distribution provision. Note that this seems to be editing a different thing than "Project" / "Edit Project" (editing "target" instead of "project"). I found I had to edit both project and target's code signing identities.

回答6:

I had exactly the same problem. It was due to installing Xcode 4.0.2 and 4.2 preview 3 at the same time. Removed both (through the provided uninstall scripts):

<Xcodedir>/Library/uninstall-devtools --mode=all

Then rebooted and installed 4.0.2 and it works :/

回答7:

I have found the codesign process a headache - I always shudder when I get am ready to use Ad Hoc distribution to beta test. After the usual round of errors and failed fix attempts I ignored the "application failed codesign" error and sent the build to a beta tester. It worked without issue.

Very frustrating.

回答8:

In the build log provided in the -UPDATE- section of the original post the root cause of the failed signature verification is expressed with the text: "test-requirement: code failed to satisfy specified code requirement(s)". That particular flavor of failed signature verification is almost always caused by mistakenly signing your app with an iPhone Developer profile instead of an iPhone Distribution profile.

It can be confirmed with the steps in "How do I verify the certificate that was used to sign my app?". If the certificate "Identity" is "iPhone Developer: YOUR_NAME" instead of "iPhone Distribution: ..." that is the reason for the "Application failed codesign verification" error, and you can resolve it by performing the following steps:

1a). if you have not yet created an App Store Distribution Provisioning Profile yet, that is done on the "Distribution" tab of the "Provisioning" Section of the iOS Portal site.

Note, the "Distribution" tab is only available to Team Members whose role is either "Agent" (the one who signed up for the iOS Developer Program), or "Admin" (those that the Agent grant access to app-distribution capabilities).

1b). if you're fairly certain you have an App Store Distribution Provisioning Profile installed in your Xcode profile library, you can verify it is an App Store profile as well as the App ID associated to it by using the steps in section How do I confirm my Provisioning Profile is for App Store distribution?

2). verify that your Scheme 'Archive' task is mapped to "Release" using the steps in section: "Creating an Application Archive"

3). check that you have an your App Store provisioning profile assigned to your "Release" Code Signing Identity using the steps in section "Assigning Provisioning Profiles to Build Configurations".

Note: it's important to make these changes at the Target level Build Settings, versus the Project level ones, as Target settings override Project ones...you can think of the Project level build settings as 'defaults' to populate target settings (and any future targets) with. Also, Ensure the "All" button is depressed in the upper-left corner of Target Build Settings to reveal the "Code Signing Identity" section.

4). retry your Product > Archive.

If the issue persists after the above, I recommend continuing onto Apple's complete list of potential causes of this error at the following URL "How do I resolve the error: Application failed codesign verification?"

回答9:

My problem was solved when I noticed that I only had a "team" provisioning profile, and the details in iOS Dev Center told me that it was not a profile fit for development because it had no device attached. So I created a second provisioning profile, which let me check the box for my device so that it had a device attached.

Then when validating or submitting the app from the Organizer window (after pressing 'Build and archive'), I first made the mistake of selecting this new profile as the code signing profile. That was wrong. The profile that worked was iPhone Developer.

Good luck!

PS: This whole submission process is a heap of abacadabra. Do you really have to create a zillion distribution profiles, provisioning profiles, etc.? It hasn't encouraged me in any way to better test my app. I already did that before I chose to upload, and clicking a hundred buttons labeled 'Create','Download' and 'Submit' isn't really a quality control process that added anything (well except being forced to buy an iPad and test on that). Who ever said iOS was developer friendly?

回答10:

My problem was that the Archive scheme did not have Build Configuration of App Store, but of Release. To change this, go to Product -> Edit scheme, select Archive on left side and change Build Configuration to App Store. I am assuming the code signing is configured properly (with distribution certificate).

回答11:

You probably created a new certificate without refreshing the provisioning profiles

回答12:

Create your iOS Distribution Provisioning Profile for App Store Distribution

回答13:

I solved this by deleting the Archive that's not validating from the Organizer, closed and reopened Xcode and built for Archiving again.

I then chose Archive from the drop down menu. After doing that my app passed validation.

Hope that helps.