Application failed codesign verification. What do I do?

Question

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)

Solution 1

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

Solution 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.

Solution 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.

Comments

[Defender Of The Code]

I checked it and set it to Automatic.

[Ben]

Under code signing identity, you need to select your code signing profile specifically.

[Ben]

Check this post for other ideas, might be to do with the validation feature: iphonedevelopment.blogspot.com/2010/05/…

[Defender Of The Code]

That article talks about AdHoc. I'm trying to get my App in the AppStore

[Ben]

Yeah the validation will run with both though. Does your app identifier match what the profile is signed for? that could also be the problem. You also might want to look inside your project pbxproj file to see if there is an error in there and its not using the profile it should be for the distribution build.

[Defender Of The Code]

I deleted all certificates and profiles from my computer. I also deleted the Apple WWDR certificate. I think I'm going to have to start over.

[n13]

Thank you so much!!!!!! In my case Entitlements.plist was selected, but invalid. I created a new one in the New File... wizard and used that instead and got rid of the above error. So a wrong entitlements.plist will produce the code sign validation error above.

[saman01]

Where is the build folder located?

[Eric]

With the latest Xcode, it is probably /Users/<user>/Library/Developer/DerivedData - I would close Xcode and drag the Build folder for your project under DerivedData to the trash. You can just delete the whole project, but that will get rid of indexes and logs - maybe not a big deal.

[Stunner]

+1 Checking the code signing settings for targets is what did it for me.

[Chrysotribax]

Hello, it's very late for an answer, but i've had a similar problem : for an unknown reason, my target "development" wanted to validate the product (as if it was a "distribution" target). Your solution works perfectly and was very clear ! thanks !