Build errors, probably a certificate issue

Since yesterday, when I try to create an AD HOC or APP Store build I get this error:

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/fanstudio/Desktop/Alfie.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 Alfie is a valid Mach executable that’s properly codesigned. (-19050)
/Users/fanstudio/Desktop/Alfie.app/Alfie: invalid signature (code or signature have been modified)

  • (null)

I didn’t do anything with my certificates, the only thing is that last week my developer subscription expired but I created the certificates again and I had no problem but now I get this error…

Anyone knows how to deal with it?

Thanks [import]uid: 89239 topic_id: 30882 reply_id: 330882[/import]

Just a Tip : Open your Xcode >> Organizer and there you login with your iTC credentials for the Organizer start to parse/fetch all your existing (in the iTC) provisioning profiles, certificates, etc.

After that process take a general look at your showed profiles and see if you notice any one that got in trouble (as red marked for example) and try to solve it “manually”.

EDIT: Also, you could take a look at this thread (http://developer.coronalabs.com/forum/2012/03/01/your-application-built-failed-pass-apples-validation-tests#comment-92804) as it would be of some value solving your problem as well.
Good luck.
Rodrigo. [import]uid: 89165 topic_id: 30882 reply_id: 123505[/import]

Hi Rodrigo, already did that and nothing changes…

It’s very strange, I never had this problem before…
[import]uid: 89239 topic_id: 30882 reply_id: 123506[/import]

Sorry to hear that.

BTW, do you know if your Distribution Certificate isn`t expired and needing renewal as well?
[import]uid: 89165 topic_id: 30882 reply_id: 123509[/import]

If I go to xCode organizer and click on my Team name both certificates have that green tick which indicates that everything is alright and they are not expired… [import]uid: 89239 topic_id: 30882 reply_id: 123512[/import]

I have tried this but it did not work…so if any suggestion please let me know…
pest control [import]uid: 177659 topic_id: 30882 reply_id: 123516[/import]

i have the same problem, can someone from corona help us sort it out please, seems to be some kind of problem when building for the app store [import]uid: 100689 topic_id: 30882 reply_id: 123518[/import]

Ok, my bad here. I was requesting the certificate with the wrong email account :slight_smile:

Everything works now.

Problem solved.

P.S. For everyone else that has trouble, did you know that Keychain Access by default is hiding the expired certificates. So, if your certificates are expired and you generated new ones you probably have duplicates now and you’d like to remove the expired ones… [import]uid: 89239 topic_id: 30882 reply_id: 123538[/import]

@adit - this sounds like a user error. It would help if you provided more details, such as when the issue started, if you’ve modified certificates or provisioning profiles recently, if sample code builds OK, etc. [import]uid: 52491 topic_id: 30882 reply_id: 123588[/import]

Just a Tip : Open your Xcode >> Organizer and there you login with your iTC credentials for the Organizer start to parse/fetch all your existing (in the iTC) provisioning profiles, certificates, etc.

After that process take a general look at your showed profiles and see if you notice any one that got in trouble (as red marked for example) and try to solve it “manually”.

EDIT: Also, you could take a look at this thread (http://developer.coronalabs.com/forum/2012/03/01/your-application-built-failed-pass-apples-validation-tests#comment-92804) as it would be of some value solving your problem as well.
Good luck.
Rodrigo. [import]uid: 89165 topic_id: 30882 reply_id: 123505[/import]

Hi Rodrigo, already did that and nothing changes…

It’s very strange, I never had this problem before…
[import]uid: 89239 topic_id: 30882 reply_id: 123506[/import]

Sorry to hear that.

BTW, do you know if your Distribution Certificate isn`t expired and needing renewal as well?
[import]uid: 89165 topic_id: 30882 reply_id: 123509[/import]

If I go to xCode organizer and click on my Team name both certificates have that green tick which indicates that everything is alright and they are not expired… [import]uid: 89239 topic_id: 30882 reply_id: 123512[/import]

I have tried this but it did not work…so if any suggestion please let me know…
pest control [import]uid: 177659 topic_id: 30882 reply_id: 123516[/import]

i have the same problem, can someone from corona help us sort it out please, seems to be some kind of problem when building for the app store [import]uid: 100689 topic_id: 30882 reply_id: 123518[/import]

Ok, my bad here. I was requesting the certificate with the wrong email account :slight_smile:

Everything works now.

Problem solved.

P.S. For everyone else that has trouble, did you know that Keychain Access by default is hiding the expired certificates. So, if your certificates are expired and you generated new ones you probably have duplicates now and you’d like to remove the expired ones… [import]uid: 89239 topic_id: 30882 reply_id: 123538[/import]

@adit - this sounds like a user error. It would help if you provided more details, such as when the issue started, if you’ve modified certificates or provisioning profiles recently, if sample code builds OK, etc. [import]uid: 52491 topic_id: 30882 reply_id: 123588[/import]

I have the same problem (full error text below) and can’t find the solution for 3 days already, driving me completely crazy.
I have revoked my certificate, deleted all provisional profiles and redone them again.
I can build non-Corona applications in XCode and sign them correctly using my distribution certificate and provisioning profile, but Corona seems to be looking for certificate in all the wrong places ?!
I am using Corona 906, XCode 4.3.1 on OSX 10.7.3
The problem first appeared when my distribution certificate expired a few weeks ago, I have obtained the new certificate, but Corona seemed to ignore it. In the meantime I have done a complete certificates/profiles clean-up TWO times, and it still doesn’t work.
@office83 -How do you mean you were requesting certificate with “wrong email account”?
Also, how can I remove the expired certificates, they no longer appear in my Keychain, should I be looking for them somewhere on my hard drive?
Thanks :slight_smile:

[code]
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/nenadkatic/Desktop/Builder.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 Builder is a valid Mach executable that’s properly codesigned. (-19050)
/Users/nenadkatic/Desktop/Builder.app/Builder: invalid signature (code or signature have been modified)

  • (null)
    [/code] [import]uid: 80100 topic_id: 30882 reply_id: 124032[/import]

SOLVED!
As I assumed Corona was fetching some expired certificates, I was only too dumb to try to look for these files the hard way through the Finder, instead of just looking at the Keychain Access’s MENU > VIEW > Show Expired Certificates.

Full info:
http://stackoverflow.com/questions/9567893/code-sign-error-certificate-identity-appears-more-than-once-in-the-keychain

I can go on with my life now… :slight_smile:
[import]uid: 80100 topic_id: 30882 reply_id: 124035[/import]

Glad you sorted this out.

My problem was when I was requesting a certificate from Keychain Access, I was using another email account of mine and the certificates generated were invalid :slight_smile:
[import]uid: 89239 topic_id: 30882 reply_id: 124039[/import]