Application failed codesign verification - over and over again... ugh!!!!!!!

No matter what I try I keep getting the following error. I am certain (i know... famous last words) that my certificate and provisioning files are setup correctly. I have also started the initial creation in iTunes connect... but no dice. Previously Corona complained about an icon that was missing even though the file name was clearly present. I "fixed" this by re-opening the icon file and re-saving. I fear that darn near anything can be throwing off the build process. Any help in determining where I should look would be GREATLY appreciated. I should probably mention that, yes, I have a paid subscription. Thanks so much!

warning: Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)
/climber.app: CSSMERR_TP_NOT_TRUSTED
- (null)

warning: Unable to extract codesigning entitlements from your application. Please make sure climber.app is a valid Mach executable that's properly codesigned. (-19050)
/climber.app: CSSMERR_TP_NOT_TRUSTED
- (null)

I noticed the following in my terminal output:

//climber.app: replacing invalid existing signature
//climber.app: CSSMERR_TP_NOT_TRUSTED
adding: climber.app/ (stored 0%)
adding: climber.app/_CodeSignature/ (stored 0%)
adding: climber.app/_CodeSignature/CodeResources (deflated 62%)

Also, I am using corona build 2011.309 and there are no spaces or non-alphanumerics in my folder names.

What is CSSMERR_TP ?

Okay... so I changed my certificates in the keychain from "Always Trusted" to "Use System Defaults" and it appears to be working. Good Grief!

Hmmm... maybe its not all good. Corona launches the Application Loader but then that tells me that there is a problem with the codesign.

I noticed that the last line printed to the terminal during the build is:

2011-03-15 23:57:08.694 Validation[14979:903] *** Warning: Defaulting to the standard codesign tool

Does this mean that the codesign actually failed?

Anyone from ANSCA able to shed some light on whether a statement of "2011-03-15 23:57:08.694 Validation[14979:903] *** Warning: Defaulting to the standard codesign tool" really indicates a build failure? Corona behaves like everything went correctly in that it offers to launch the app uploader after the build completes.

When you build for the app store Corona spits out two versions, a zip file and the app. Throw the zip file in the trash and zip up the app yourself by right clicking on the app and Compress "whatever".

Then try again with Application Loader.

Hope this helps.

That worked!!! Thank you sooooo much!

Glad I could help :)

I am getting the:
"Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate."

I only see one file that Corona produces. I right click and compress it. I do have a valid certificate. any other ideas? I changed my Application Loader to ver 3. because version 4 was giving a "dwarf" error.

I am so close but so far.

I had the same problem. I used build 318. Deleted zip and compress the app to create new zip. Upload worked great. Something wrong with build option in Corona SDK.

Deleting the zip file and making my own worked for me too. I'm using Corona build 312. Thanks for the tip.

"Deleting the zip file and making my own"

it works for me also...thanks

I found that code signing of Xcode does not support network account.
-- Advanced UI + Graph for Corona® | Website | Forum (https) | See:

Fix for Codesign Failure

I finally got ready to put my game on the App Store and created my Distribution Provisioning Profile. But when I built for iOS using that profile in the Code Signing Identity, I got the dreaded Application Failed Codesign Verification message.

Here are the steps I did to get my build to finish without an error.

1. Go to the Keychain Access Program.

2. Under "login" and "Certificates" first make sure you have the complete and correct collection of certificates.

3. Right click the iPhone Developer certificate and select "Get Info"
Under the "Trust" section make sure "When using this certificate" is set to "Use System Defaults".

4. Click the caret for the iPhone Developer sub category
Double click on the private key and set "Access Control" to "Allow all bla bla bla....."

5. Right click the iPhone Distribution certificate and select "Get Info"
Under the "Trust" section make sure "When using this certificate" is set to "Use System Defaults".

6. Click the caret for the iPhone Distribution sub category
Double click on the private key and set "Access Control" to "Allow all bla bla bla....."

After these steps, a test build still generated the same error. Next I did this:

7. Right click the Apple Worldwide Developer Relations Certificate and select "Get Info"
Under the "Trust" section make sure "When using this certificate" is set to "Use System Defaults".

After this last step, the iOS build finished successfully. I did not go back to reverse steps 3 through 6, so I don't know if they were necessary or if the final step 7 was sufficient in itself.

Also, the Corona SDK generated zip file was successfully uploaded to iTunes Connect without a problem; I did not have to delete the zip file and makemy own. I'm using SDK build 484.

I've done everything noted above, and I still get:

warning: Application failed codesign verification. The signature was invalid, or it was not signed with an iPhone Distribution Certificate. (-19011)

I'm still searching everywhere online, looking for the fix. If anyone has any suggestions in addition to what is posted above, I'd so appreciate hearing about it.

Naomi are you getting this error from Corona when you build or from Apple when you go to upload?

If it is from Apple on upload then you could have a file in your build with a name that is "reserved". (For example I have seen this error from Apple when you name a folder in your project "resources".)

Is it possible you are doing anything like that? Are you getting any errors in the terminal during the build process?

Peach :)

Hi Peach, thanks for asking. I get the error/warning from Corona simulator when I build with Dev Certificate. I don't get any error or warning when I build with Distributor Certificate or Ad Hoc Certificate.

Early on, I had errors that appeared on terminal. But I've cleaned them out (by clean slating everything, such as my keychain, dev certificate, distribution certificate, ad hoc certificate, and all the provisional profiles, plus uninstalling Xcode, rebooting and reinstalling). I no longer see any errors on terminal when I build the game using Corona simulator.

Only thing I see is the warning message (noted above) that pops up at the very end of the build process using dev certificate. (No message pops up when I use distribution or ad hoc certificate.) I can still install the dev build made with this warning and play it on my device.

I looked around the web, and most of the people seem to complain about the problem with distribution build (being a show stopper for them from publishing their app/game).

My issue is, without the dev build properly generated and installed on my device, I can't test my In-App Purchase. After almost 10 days of hair-pulling effort, I'm about to give up.

The very last thing I did was to generate a clean distribution build, delete the previously generated In-App Purchase products in iTunes Connect and create new ones, upload the binary, and reject it. At this point, unless I'm offered a solution that I have not thought of, only hope I have is to try again a few days from now, and see if the problem simply disappears on its own accord. Otherwise, I'll simply move on and take the route of releasing a free lite version and a paid/premium version separately.

Naomi, I'm having the same problem. Which is weird because Corona built my app with no problem last night just after midnight. I tried submitting it to Apple this morning and I received an error that the app failed codesign verification. I tried having Corona rebuild the app, but now Corona's giving me the same error that you've received. So I don't know what's going on.

Aha, I figured it out! Apparently I hadn't set up my Distribution Profile properly. I made a new one by following the instructions on the Developer Support site and that fixed the problem. Phew.

@samsaturday, glad to hear your problem is solved. My problem is code signing with my Developer Certificate. When I build with Distribution Certificate (both app store ready and ad hoc versions), I get no error messages or warnings...

views:6300 update:2011/10/19 14:58:09
corona forums © 2003-2011