Validation problem with new Corona public build - invalid signature/codesign wrapper problems

nate2 · December 11, 2012, 10:37am

I have been using Corona build 2012.840, but just switched to 2012.971. Building for device worked fine (builds passed the Apple verification tests fine) and I haven’t changed anything else other than the Corona build being used (still using the same valid provisioning profile). Now, when I try to build, I get these errors:

failed to extract requirements data: 1
/Users/Nate/Desktop/MyGame.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)
[import]uid: 135391 topic_id: 33878 reply_id: 333878[/import]

nate2 · December 11, 2012, 11:10am

Additionally, when I try to add the new build to the device, I get a “The application does not have a valid signature.” error.

Why would the signature have changed when I updated Corona? [import]uid: 135391 topic_id: 33878 reply_id: 134656[/import]

Naomi · December 11, 2012, 11:55am

It certainly sounds strange. Do you get no errors if you go back to using 840? If 840 also gives you the same errors, then it might be that your certificate has expired very recently, invalidating the provisioning profile.

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134666[/import]

nate2 · December 11, 2012, 11:57am

No, I get no errors when using 840. Just went back and re-built with it and it is fine. [import]uid: 135391 topic_id: 33878 reply_id: 134667[/import]

ken4 · December 11, 2012, 12:25pm

Hmm, I get this error:

"Disallowed signer
AssertMacros: cms_verify(signature, code_directory, certificates), file: codesign_wrapper.c, line: 777
AssertMacros: verify_code_signatures(code_signatures, certificates), file: codesign_wrapper.c, line: 946

(null)"

The title says “Your application built but failed to pass Apple’s validation tests.”

I’m using Version 2012.972 (2012.11.28)

Any ideas? [import]uid: 72317 topic_id: 33878 reply_id: 134676[/import]

ken4 · December 11, 2012, 1:05pm

I think I got past this. For some reason there are 3 seemingly identical provisioning entries in the pop-up list in the iOS build dialog. I get the above error when using the first entry but not when using the second or third.

Even though these all have the same name, do these entries correspond to the ad-hoc, development and distribution provisioning licenses mentioned elsewhere in the docs? If so it would be nice to identify them as such. [import]uid: 72317 topic_id: 33878 reply_id: 134682[/import]

nate2 · December 11, 2012, 1:58pm

My issue seems to be different from Ken4’s. I don’t see multiple provisioning entries in the iOS build dialog. [import]uid: 135391 topic_id: 33878 reply_id: 134688[/import]

Naomi · December 11, 2012, 3:32pm

@ken4, launch Xcode and check the provisioning profiles listed under Windows > Organizer. It’s the very first in the Organizer window under LIBRARY section. You’ll see all the provisioning profiles, and you should just delete/remove the ones that are no longer valid. And then, relaunch Corona Simulator. Once removed from Xcode, the invalid provisioning profiles should not appear in the drop-down when generating a build. If you don’t see any provisioning profiles, click on Refresh at the lower right corner, which will import all of your provisioning profiles for you, and then you can isolate and remove the ones you don’t want.

Edit: By the way, you can rename the provisioning profiles at Apple Dev center. Once you rename it to more recognizable names, you shouldn’t have any trouble selecting the one you want to use.

@nate2, I’m not very sure why it’s happening to you, but just in case… are you using the latest version of Xcode? I don’t remember exactly when the Xcode upgrade requirement took place in relative to Corona builds, but I remember at some point this year, the Xcode update was necessary to build for more recent version(s) of iOS. I believe it was Apple’s mandate. My Xcode version is 4.5 and I have no issue generating device builds.

Edit: @nate2, I’m now wondering if you are having the very same problem kurtbieg is having. Please see his post here (and ensuing posts). Sounds like a nightmare (just like the one I had with renewing my certificate yesterday):
http://developer.coronalabs.com/forum/2012/11/30/error-message-popup-when-first-time-use-xcode-452-build-971#comment-134700

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134690[/import]

nate2 · December 11, 2012, 4:05pm

Thanks, Naomi. Yes, it looks like the same problem as kurtbeig’s. I apparently fixed it, though. I was already running XCode 4.5, but I just updated to 4.5.2 and I’m not getting the error anymore. Very strange. [import]uid: 135391 topic_id: 33878 reply_id: 134720[/import]

Naomi · December 11, 2012, 4:20pm

Hey, nate2, glad to hear you got it fixed!!

Naomi

P.S. BTW, yeah, this whole thing about code-signing is nightmarish. My certificate expired a couple of days ago, and getting it renewed required me to completely clean slate my keychain. Yikes. But at least I didn’t have to reinstall OSX, which, apparently, some other user had to do to get it to work. [import]uid: 67217 topic_id: 33878 reply_id: 134724[/import]

ken4 · December 11, 2012, 4:36pm

Hi Naomi,

Thanks for the response and the insights. I’ll revisit this shortly and see if I can get it all working as you suggest with distinct names, etc.

Cheers!

Ken [import]uid: 72317 topic_id: 33878 reply_id: 134726[/import]

ken4 · December 12, 2012, 1:44am

I think I got it all working with the provisioning files, etc. on multiple devices. Tomorrow, onto trying to actually submit the app to the App Store. Hopefully the screenshots I’ve taken are acceptable resolution/size-wise…

Cheers! Ken [import]uid: 72317 topic_id: 33878 reply_id: 134785[/import]

Naomi · December 12, 2012, 9:14am

@Ken, glad to hear it. Good luck with the app submission & approval process!

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134844[/import]

ken4 · December 12, 2012, 11:09am

Hi Naomi,

I think I just successfully submitted my app! Now to see what happens with the review process.

Just to verify, once I setup the app in iTunes Connect and then upload the app using the Application Loader tool, the status of my app is “Upload Received”. Is that correct and I now simply wait for an approval email or is there anything else to do?

Also I didn’t have a dedicated support website so I put in a temp link and will create one shortly. Anything specific I need to put on that page?

Thx!

Ken [import]uid: 72317 topic_id: 33878 reply_id: 134864[/import]

Naomi · December 12, 2012, 11:55am

Hey, Ken, I believe “Upload Received” will eventually change to something else. I don’t remember what exactly. But it sounds like you’ve taken the right steps to me.

About the support link, I don’t remember reading any specific requirements for it, but you may want to at least include how your users may contact you. You could also include FAQ (if you think there’s going to be a lot of common questions your users might bring up?) With Beetle Bounce, I gave it the URL for our main contact page.

Here’s the Beetle Bounce’s iTunes screen, and notice “Beetle Bounce Support” link. It launches the URL I supplied:

https://itunes.apple.com/app/id471409331?mt=8

I hope this helps.

Good luck!

Naomi
[import]uid: 67217 topic_id: 33878 reply_id: 134868[/import]

ken4 · December 12, 2012, 2:53pm

Hi,

Yup, I received an email and it changed to “Waiting for Review”.

Thanks for the notes on the web support page. I’ll implement that later today!

Cheers, Ken [import]uid: 72317 topic_id: 33878 reply_id: 134887[/import]

nate2 · December 11, 2012, 11:10am