Application Failed Codesign Verification

Solar2D iOS
#21

I’m getting the same message after renewing developer and distribution profiles.

The dev and dist profiles are sitting in my X Code Organiser > Library > Provisioning Profiles area, but not in Organiser > Devices > My Mac…should they be? (The dev ones are in the Devices > iPad area). When I got the new profiles from iOS dev centre I just double clicked on them in Download folder as usual and they appeared in the organiser with green circle and white tick valid profile icons.

In Xcode > Organizer > Devices > iPad there is an amber circle next to it, not green. Does that mean anything? I’ve tried re-booting the iPad, doesn’t change the color to green. OS on iPad is 6.1.3 (10B329), the Xcode iOS system says latest. I’m not too fussed about testing on the iPad at the moment, just want to get a validated build over to apple.

Here’s the Corona message I get after attempting to build:

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

/Users/markjholme/Desktop/iOS/The CastleGhost/TheCastleGhost.app: 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 TheCastleGhost is a valid Mach executable that’s properly codesigned. (-19050)

/Users/markjholme/Desktop/iOS/The CastleGhost/TheCastleGhost.app/TheCastleGhost: invalid signature (code or signature have been modified)

 - (null)

#22

Fixed above with upgrade to Xcode 4.62 on Mac

However now getting a whole bunch of alerts in application uploader - shall investigate and update…cheers

#23

Updating to 4.6.2 and refreshing Provisioning Profiles in Organizer didn’t fix my issue above. Note that it did work with the same provisioning profiles on another machine running XCode 4.6.1.

You’d think a big company like Apple could do better than to return generic error codes from something as important as a security function. If they had, we would have had the cause for the error by now.

#24

Well, I closed everything and restarted my Mac and the application loader went through fine on the second attempt, accepted the app fine.

So it seems my procedure should have been:

Up date Xcode

Delete all certs and profiles that had expired

create new certs and generated new profiles and upload them

open Corona and build

keep fingers crossed!

#25

Yikes. I’ve done everything here except for update xcode (I’m running xcode 4.4.1 on OSX 10.7.4)

I deleted all certificates and provisioning profiles from the apple site, and from my local machine, then recreated just a single Distribution cert, and an ad hoc distribution profile from scratch (using the guide Brent linked to, just to be safe), and imported them into my keychain.

When I try to build for iOS, I’m still getting the same errors as others have mentioned.

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

/Users/producerism/Desktop/EscapefromJekyllIsland.app: 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 EscapefromJekyllIsland is a valid Mach executable that’s properly codesigned. (-19050)

/Users/producerism/Desktop/EscapefromJekyllIsland.app/EscapefromJekyllIsland: invalid signature (code or signature have been modified)

 - (null)

I’m running out of ideas…  I’ll do a full system update (along with xcode) later today as a last-resort attempt.  Is there some step I’m overlooking?  I feel like I’ve followed all of the steps others have outlined in the multiple threads on this very issue, but haven’t gotten to the same resolution everyone else does.

#26

I think the XCode is too old.  4.6.2 is the latest version, 4.4 is 2 major builds behind and I don’t know how well we are going to work with that old of an Xcode.

#27

I have had this happen to me several times, it seems to happen the most when certificates are expired (like when your yearly apple developer renewal) or right after I have done an xcode update.

Kill (delete) all your certs and provision files in xcode.

Regenerate fresh ones for everything on the apple dev site

start xcode (enter organizer) and force it to refetch everything from apple.

#28

It was most likely an Xcode issue.  I updated Xcode to the latest, and OSX to 10.8.3 as well, just for the hell of it.  Smooth sailing now, thanks.

#29

This is confirmed working with XCode 4.6.1, OSX 10.8.2, Corona 2013.1076.

However, on my secondary machine (also a Mac and the exact same specs as above - and with the same development and distribution profiles installed), I can build for iOS Device but not for iOS Distribution:

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

/Users/blah/Documents/blah.app: 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 blah is a valid Mach executable that’s properly codesigned. (-19050)

/Users/blah/Documents/blah.app/blah: invalid signature (code or signature have been modified)

 - (null)

Why do I get this for Distribution but not for Development? The Distribution profile was created with the same bundle ID, uses the same development certificate, and they are all valid in XCode. I can build for iOS Distribution in XCode fine on both machines (for other apps, obviously).

The only thing I can think of that differs is something in KeyChain, but… can’t I rule that out since I can Distribute in XCode and Develop in Corona?

It says signature has been modified, well I haven’t modified it! 

Has Apple disclosed exactly what entries in KeyChain and Organizer are involved in code signing? If there was such a list I could compare all of them and find the differences.

Just trying to reason it out. What things could I eliminate?

#30

I’m getting the same message after renewing developer and distribution profiles.

The dev and dist profiles are sitting in my X Code Organiser > Library > Provisioning Profiles area, but not in Organiser > Devices > My Mac…should they be? (The dev ones are in the Devices > iPad area). When I got the new profiles from iOS dev centre I just double clicked on them in Download folder as usual and they appeared in the organiser with green circle and white tick valid profile icons.

In Xcode > Organizer > Devices > iPad there is an amber circle next to it, not green. Does that mean anything? I’ve tried re-booting the iPad, doesn’t change the color to green. OS on iPad is 6.1.3 (10B329), the Xcode iOS system says latest. I’m not too fussed about testing on the iPad at the moment, just want to get a validated build over to apple.

Here’s the Corona message I get after attempting to build:

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

/Users/markjholme/Desktop/iOS/The CastleGhost/TheCastleGhost.app: 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 TheCastleGhost is a valid Mach executable that’s properly codesigned. (-19050)

/Users/markjholme/Desktop/iOS/The CastleGhost/TheCastleGhost.app/TheCastleGhost: invalid signature (code or signature have been modified)

 - (null)

#31

Fixed above with upgrade to Xcode 4.62 on Mac

However now getting a whole bunch of alerts in application uploader - shall investigate and update…cheers

#32

Updating to 4.6.2 and refreshing Provisioning Profiles in Organizer didn’t fix my issue above. Note that it did work with the same provisioning profiles on another machine running XCode 4.6.1.

You’d think a big company like Apple could do better than to return generic error codes from something as important as a security function. If they had, we would have had the cause for the error by now.

#33

Well, I closed everything and restarted my Mac and the application loader went through fine on the second attempt, accepted the app fine.

So it seems my procedure should have been:

Up date Xcode

Delete all certs and profiles that had expired

create new certs and generated new profiles and upload them

open Corona and build

keep fingers crossed!

#34

I just had this problem today. The solution for me was found in another topic on the forum; I’ll post it here in case anyone else stumbles across this post like I did:

Open KeyChain Access application
Select the ‘login’ keychain, and select in the bottom pane ‘Certificates’
Switch to the ‘system’ keychain and see if there are certificates registered in both chains.
Remove one copy of them (I removed the one from system)
Rebuild the application

#35

I just had this problem today. The solution for me was found in another topic on the forum; I’ll post it here in case anyone else stumbles across this post like I did:

Open KeyChain Access application
Select the ‘login’ keychain, and select in the bottom pane ‘Certificates’
Switch to the ‘system’ keychain and see if there are certificates registered in both chains.
Remove one copy of them (I removed the one from system)
Rebuild the application

#36

Hope this helps too…

Been having exactly the same error when trying to build a developer test version for my iPad.

Deleted ALL Certificates and Profiles (some HAD expired) from iOS Dev Portal and XCode and Keychain Access and started again but STILL got the error! :(  I looked everywhere in Keychain Access and cound NOT find a duplicate of anything! :(  EVENTUALLY, had a look through the Keychain Access Menus and found a “Show Expired Certificates” option!! Selected this and low-and-behold there was a duplicate and expired iPhone Developer Certificate in “my” keychain (the one that has my own name, under “login”) Deleted it, ran Build from Corona again and held my breath… and exhaled deeply with a big smile when it worked!!! :slight_smile:

#37

Hope this helps too…

Been having exactly the same error when trying to build a developer test version for my iPad.

Deleted ALL Certificates and Profiles (some HAD expired) from iOS Dev Portal and XCode and Keychain Access and started again but STILL got the error! :(  I looked everywhere in Keychain Access and cound NOT find a duplicate of anything! :(  EVENTUALLY, had a look through the Keychain Access Menus and found a “Show Expired Certificates” option!! Selected this and low-and-behold there was a duplicate and expired iPhone Developer Certificate in “my” keychain (the one that has my own name, under “login”) Deleted it, ran Build from Corona again and held my breath… and exhaled deeply with a big smile when it worked!!! :slight_smile:

#38

rbreve is right, I had the same problem, now it resolved

#39

rbreve is right, I had the same problem, now it resolved