Invalid code verification. What am I doing?

Question

Xcode gives me this warning when I create an application for release.

Invalid code verification. The signature was invalid or was not signed with the Apple Certificate of Submission. (-19011)

Do I need to delete all entries from my keychain and retry obtaining a certificate, preparation profile, etc.

I can create and debug iPhone and iPad without any problems.

If you know how I can solve this dilemma, provide the exact steps or way to contact you about this.

thanks

---- UPDATE -----

Build log

Confirm assembly / 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: checking for failed application code. The signature was invalid or was not signed with the Apple Certificate of Submission. (-19011) Executable = / Users / iosdeveloper / Documents / Programming / iPad / iApp HD / build / Release-iphoneos / iApp.app / iApp codesign_wrapper-0.7.10: using Apple CA to evaluate the profile / 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: meets the requirements Test requirement : Failed to satisfy code requirements (s) codesign_wrapper-0.7.10: Failed to execute code (1) - (null)

Answer 1

You probably need to check which code signing profile is selected in the distribution build properties.

Answer 2

Here is the checklist that I look through when I hit this:

• Clear all targets, exit Xcode, and then drag the build folder from your project to the trash.

• Make Get Info in your project, make sure that the code signing rights and code signing identification are selected correctly. Do the same for your goals.

• Log in to the Provisioning Portal and verify that the distribution certificate has not expired. Also check the distribution distribution profile and make sure it is active. Make sure that the certificate is correctly specified in your keychain and that the distribution profile is in Xcode Organizer (if you have several identical ones, delete everything except the correct one and repeat step # 2).

• Look at your build results for failure and determine which profile it is using and make sure it is correct.

Answer 3

It looks like your goal is “Development,” but Xcode applied some distribution parameters to it, so this warning simply means that your ad assembly does not have a valid AppStore submission certificate. Go to your target settings, select the Release setting and uncheck the box next to “Check embedded product”.

Answer 4

Create an iOS distribution distribution profile for distribution on the App Store

Answer 5

Invalid code verification. The signature was invalid or was not signed with the Apple Certificate of Submission. (-19011) I have the same warning ...

I just switched to iOS. The deployment target 4.3 - 3.2.2 works great.

Answer 6

Note: you may need to go to the Xcode "Project" and select "Edit Active Target (appname)", which is at the bottom of the list ... in the new window that opens, select "Build", then in the "Code Signature Identification" section select your distribution. Note that this seems to be for editing something other than “Project” / “Edit Project” (instead, editing the “target” of the “project”). I found that I needed to edit the signing identifiers of the project code and the target code.

Answer 7

I had exactly the same problem. This was due to installing Xcode 4.0.2 and 4.2 preview 3 at the same time. Both were deleted (via the provided removal scripts):

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

Then it reboots and installs 4.0.2, and it works: /

Answer 8

I found that the code processing process is a headache - I always tremble when I am ready to use the Ad Hoc distribution for beta testing. After the usual round of errors and unsuccessful attempts to fix, I ignored the application error with the error and sent the assembly to the beta tester. It worked without problems.

Very frustrating.

Answer 9

In the assembly log contained in the -UPDATE section of the original message, the root of the cause of the signature verification error is expressed by the text: "test-requirements: code could not fulfill the specified code requirements (s)" . This particular taste of unsuccessful signature verification is almost always caused by the erroneous signing of your application with an iPhone Developer profile instead of an iPhone distribution profile.

You can confirm this with the steps. How can I verify the certificate that was used to sign my application? ". If the certificate" Identity "is" iPhone Developer: YOUR_NAME "instead of" iPhone Distribution: ... ", then this is the cause of the error " Error in application code codes failed " , and you can resolve it by following these steps:

1a). if you haven’t already created an App Store distribution distribution profile that runs on the Distribution tab of the Provisioning section of the iOS Portal site .

Note The Distribution tab is available only to Team members whose role is either Agent (the one who signed up for the iOS Developer Program) or Administrator (those that Agent provides access to application distribution capabilities).

1b). if you are confident that you have the App Store distribution profile profile installed in your Xcode profile library, you can verify that it is a profile in the App Store, as well as its associated application identifier, using the steps in How to Confirm My is the Provisioning Profile for distribution on the App Store?

2). make sure that your “Archive” task is mapped to “Release” using the steps in the section: “ Creating an application archive ”

3). make sure you have an App Store profile profile assigned to your “Release” Code Signing Identity using the steps in the “ Assigning Profiles to Create Configurations ” section.

Note : it is important to make these changes to the settings of the "Configure" level compared to the levels of the project level, since the "Parameters" parameters override the project ... you can think of the project level, create the parameters as "default" to fill in the target settings (and any future goals). In addition, make sure that the "All" button is clicked in the upper left corner of the settings of the target assembly to open the "Code Identification" section.

4). try your product again> Archive.

If the problem persists after the above, I recommend continuing the full list of possible causes of this error in Apple at the following URL. How to fix the error: Error checking application code?

Answer 10

My problem was resolved when I noticed that I only have a “team” profile, and the details in the iOS Dev Center told me that this is not a profile suitable for development, because it is not connected to the device. Therefore, I created a second provisioning profile that allows me to check the box for my device so that it connects to the device.

Then, when checking or sending the application from the "Organizer" window (after clicking "Build and Archive"), I first made a mistake by choosing this new profile as the code signature profile. This was wrong. The profile that worked was iPhone Developer.

Good luck

PS: This whole filing process is a bunch of abacadabra. Do you really need to create zillion distribution profiles, customization profiles, etc.? This did not in the least encourage me to test my application better. I already did this before I selected the download, and clicking on the one hundred buttons labeled “Create,” “Upload,” and “Submit” is not really a quality control process that added something (well, besides, that you have to buy an iPad and test for what). Has anyone ever said that iOS supports the developer?

Answer 11

My problem was that the App Store configuration was not configured in the archive scheme, but in the Release version. To change this, go to “Product → Change Scheme”, select “Archive” on the left and change “Assembly Configuration” in the “Application Store”. I assume that code signing is configured correctly (with distribution certificate).

Answer 12

You probably created a new certificate without updating provisioning profiles

Answer 13

I solved this by deleting the archive, which is not confirmed by the Organizer, closed and opened Xcode again and created again for archiving.

Then I selected Archive from the drop down menu. After that, my application passed the test.

Hope this helps.