Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed wit

mrctito · March 31, 2012, 1:26pm

Dear sirs,

Could you, please, help me with this issue?

I am using latest version of Xcode (4.3.2) and Corona Daily Build (31/03/2012)

I have already re-created license, provisioning profiles, etc…
warning: Application failed codesign verification. The signature was invalid, contains disallowed entitlements, or it was not signed with an iPhone Distribution Certificate. (-19011)
failed to extract requirements data: 1
invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 880

(null)

warning: Unable to extract codesigning entitlements from your application. Please make sure is a valid Mach executable that’s properly codesigned. (-19050)
/ invalid signature (code or signature have been modified)

(null) [import]uid: 62613 topic_id: 24184 reply_id: 324184[/import]

_RSCdev · March 31, 2012, 9:45pm

It sounds like you`re not building the app using your Distribution certificate at first glance. Are you sure about using that to build for store?
Cheers,
Rodrigo. [import]uid: 89165 topic_id: 24184 reply_id: 97637[/import]

peach_pellen · March 31, 2012, 11:19pm

This would be the first thing I’d check too, that you’re using Distribution certificate and provisioning profile.

Also if you have CFBundleIdentifier in your build.settings file it may be well worth removing it. [import]uid: 52491 topic_id: 24184 reply_id: 97651[/import]

alan_mcnd2 · April 7, 2012, 1:13pm

did you fix it?
I got the same problem here
[import]uid: 76993 topic_id: 24184 reply_id: 99247[/import]

Tom · April 7, 2012, 1:23pm

Try renaming your build.settings file and see if you get the error. If no error, look for something in that file that is causing the problem.

Also try a simple app name in the build window to see if that is causing the problem (e.g. Testapp). [import]uid: 7559 topic_id: 24184 reply_id: 99250[/import]

markg · April 10, 2012, 2:25pm

Hi,
did anyone fix this problem? I get the same error. Tried renaming build.settings, didn’t help. I tried to build the HelloWorld sample but get the same error.

Thanks
Mark [import]uid: 93426 topic_id: 24184 reply_id: 99874[/import]

payjo · April 12, 2012, 9:02am

Anyone find a solution for this? Everything was working fine with build 654, but I upgraded to 782 for the iPad 3 retina support and now I’m getting this error. Also upgraded to OS X 10.7.3.

Things I’ve tried:

Creating a new ad hoc distribution provisioning profile
Building a sample app
Using a simple app name

Thanks,
Steve [import]uid: 8919 topic_id: 24184 reply_id: 100347[/import]

peach_pellen · April 12, 2012, 12:04pm

Make sure you have updated Xcode and to the latest version of Application Loader via Apple website and Java via Software Update.

@Steve - to isolate the issue do a test build with latest stable version of Corona and let us know if the issue still exists. (I don’t believe it’s a build issue.) [import]uid: 52491 topic_id: 24184 reply_id: 100395[/import]

markg · April 12, 2012, 12:08pm

Thanks, so do you recommend to update to Xcode4.3?

Mark [import]uid: 93426 topic_id: 24184 reply_id: 100398[/import]

payjo · April 12, 2012, 2:11pm

@Peach I tried with the stable build yesterday and decided to try again with the most recent daily build.

You think this could be solved if I got premium support? I rather have a Corona expert dive into this issue. [import]uid: 8919 topic_id: 24184 reply_id: 100438[/import]

peach_pellen · April 13, 2012, 1:55am

Markg, yes, if you’re running Lion updating is a good idea - not least because it’s needed to install on devices running iOS 5.1 IIRC.

Steve, I take it the stable build didn’t work? If you have ensured your certificates and provisioning are fine and checked your build.settings doesn’t include CFBundleIdentifier then you should consider using this support form: http://developer.anscamobile.com/content/bug-submission

Someone will look at your project and confirm it’s not a user issue; if it turns out to be certificates needing fixing then they will advise you to go the premium support route to have someone work with you 1-on-1 to find and fix the issue.

Peach [import]uid: 52491 topic_id: 24184 reply_id: 100503[/import]

payjo · April 13, 2012, 7:58am

Thanks Peach! I will try that. Appreciate the help. [import]uid: 8919 topic_id: 24184 reply_id: 100569[/import]

Jalmood · April 18, 2012, 11:15am

@mrctito

I recommended you to follow these instructions in the following post.
http://developer.anscamobile.com/forum/2011/03/16/application-failed-codesign-verification-over-and-over-again-ugh#comment-34399

I had the same problem [import]uid: 45018 topic_id: 24184 reply_id: 101922[/import]

Huang_Wei · June 6, 2012, 11:14pm

I got exactly the same problem, I’m using the newest daily build (828). I updated Xcode (4.3.2), Application loader (2.3.2) and JDK last month. And I have recreated all the distribute certificate profile, all the distribution provision files from scratch, but still got the same error.

From the log messages displayed oncorona terminal, the validationTool is called right after a lot of adding .... (stored xx%), no message about signing or something. [import]uid: 38415 topic_id: 24184 reply_id: 110595[/import]

peach_pellen · June 7, 2012, 12:37am

Hey Huang,

To confirm, are you getting an error from Corona once the app is finished building or from Apple when trying to upload? [import]uid: 52491 topic_id: 24184 reply_id: 110599[/import]

Huang_Wei · June 7, 2012, 12:57am

Hello peach, in my case it is the Corona gives the warning message after building. (If i try to upload to appstore anyway, AppLoader gives a similar error). [import]uid: 38415 topic_id: 24184 reply_id: 110604[/import]

Huang_Wei · June 7, 2012, 1:46am

Solved my part of the problem. Seems that Corona did send a warning message to the terminal but because the screen was soon be flooded by a lot of adding ... messages i did not noticed at the first time.

The message says there are two certificate profiles have the same name, one under the system folder (/Library/…) and one under my home folder (/Users/myname/Library/…), I think this is a problem stemmed from the upgrading of Xcode 4 quit before, but didn’t cause building error because the elder certificate dose not expire for a while.

I chose a quit gruff approach by deleting all public/private keys and certificates from the keychain tool and re-generate them all over from scratch (done quick than it sounds), and now I can upload binaries to AppStore again. [import]uid: 38415 topic_id: 24184 reply_id: 110622[/import]

peach_pellen · June 7, 2012, 5:33am

Hey again Huang,

I’m glad to hear you were able to resolve this; thank you for posting a follow up.

Peach [import]uid: 52491 topic_id: 24184 reply_id: 110649[/import]

jleap · October 9, 2012, 1:18pm

Wow, this is a well documented error issue with so many different solutions. Please help… have tried many of the suggestions I have found online.

HERE IS THE ERROR MESSAGE:
failed to extract requirements data: 1
/Users/: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 879

(null)

warning: Unable to extract codesigning entitlements from your application. Please make sure X is a valid Mach executable that’s properly codesigned. (-19050)
/Users/X: invalid signature (code or signature have been modified)

(null)
I get this error when I try to build for development. Recently this was working fine, making provisioning apps… nothing except my Corona subscription has been expired/updated.

I have no duplicate keychains or certificates and everything is active. I have deleted and downloaded new provisioning certificates. I have not revoked and recreated in the provisioning portal… scared of really messing things up if there is a simple solution I don’t know about.
FYI, I can not build any of the sample apps w/o getting the error warning as well. However, it does make a build icon despite error that fails to install on my device.

Not sure how provisioning can be working one day and not the next…
Your help is getting over this hurdle is appreciated.
Kind Regards, Jamie
[import]uid: 10840 topic_id: 24184 reply_id: 126918[/import]

peach_pellen · October 10, 2012, 12:08pm

You don’t need to revoke provisioning, you need to delete provisioning from Xcode organizer (ALL of them) then delete all certificates (for iOS dev obv) from keychain. Then recreate certificates and renew/redownload and install provisioning profiles.

Make sure you did all of that, in the order - and if you have then check to make sure you aren’t using any reserved names as sub folder names. [import]uid: 52491 topic_id: 24184 reply_id: 127019[/import]