Build 2011.335 had broken code signing

Well the first time I submitted an iPad App it was pretty easy. Having upgraded today to Build 2011.335 I was encouraged to see a direct “Submit App” button that points to App Loader. Having submitted 3 previous versions, I know my Certificates are good.

Now I get these error messages from the Apple App Loader:
The CodeResources file must be a symbolic link to _CodeSignature/CodeResources.
Application failed codesign verification. The signature was invalid, or it wsa not signed with an Apple submission certificate.

In process, the compiler did say:
2011-03-30 17:14:45.814 Validation[20274:903] *** Warning: Defaulting to the standard codesign tool
I am going to revert to the 2011.267 Build and hope that works better. [import]uid: 6114 topic_id: 8442 reply_id: 308442[/import]

I did revert to Build 2011.268 and that seems to work fine, now “Waiting for Review” as expected.

Note that the “Edit” function of this Forum software will not allow an edit, complaining about Forum selection, which neither selection is acceptable…

[import]uid: 6114 topic_id: 8442 reply_id: 30245[/import]

I was getting the same error message when trying to submit an update for my app with daily build 2011.318. I ended up getting it to work by deleting the zip file that corona now automatically makes and just zipped the app myself. [import]uid: 5786 topic_id: 8442 reply_id: 30260[/import]

If zipping up the app yourself works, then I suspect that we missed something when we zipped it up for you. It might be something like a command line switch we missed when we call zip. (I presume you are using Finder to zip it which might invoke different switches by default.)
Would you guys submit a bug report to:
http://developer.anscamobile.com/content/bug-submission

Please include the zip file you create and the zip file we create so we can compare the difference.

[import]uid: 7563 topic_id: 8442 reply_id: 30451[/import]

I will copy what I wrote above as a bug report, but long got rid of the buggy ZIP file.

Thanks for paying attention to this show-stopper bug. [import]uid: 6114 topic_id: 8442 reply_id: 30454[/import]

Tried to create a bug report but it wouldn’t let me upload my zip files because they were too large? [import]uid: 5786 topic_id: 8442 reply_id: 30487[/import]

Hi,

got the same… Iam using the last build Version 2011.336 (2011.1.20)

But i don’t know witch .zip file you mean… i only got the .app from corona build.

Then i zip it myself but the Application loader says:
Application failed code-sign verification, signature invalid…

Compiler output:
…: replacing invalid existing signature
/…: signed bundle with Mach-O universal (armv6 armv7) […]
2011-04-02 09:59:06.236 Validation[1865:903] *** Warning: Defaulting to the standard codesign tool
:frowning: [import]uid: 9592 topic_id: 8442 reply_id: 30512[/import]

Ok i didn’t use the distribution profile…
so if u use the right one… than you will get 2 one zip and one app

the zip didn’t work… but delete and create one by my self works!!

BR
Alen [import]uid: 9592 topic_id: 8442 reply_id: 30518[/import]

The automatic build and zipping of the .app file is broken in the latest version of Corona. I tried and tried, but finally resorted to taking the app file myself, zipping it myself, and submitting via the application loader manually - worked as expected my latest app is waiting for review.

Just an FYI - when you build using the signed distribution cert the Corona compiler will build two files, a regular .app file and a new .zip file for uploading, but again - the zip isn’t right.
[import]uid: 9046 topic_id: 8442 reply_id: 30700[/import]

Sorry about the size limit. I’m going to try to get that raised. For future reference, how large was your binary?

FYI, I just pushed in a fix for this.
[import]uid: 7563 topic_id: 8442 reply_id: 30709[/import]

Well since you wanted both versions of the zip files and I couldn’t see a way to submit more than 1 zip file in the bug reports I zipped them both together and that clocked in at around 22.3 MB, Just over 11 MB for each. [import]uid: 5786 topic_id: 8442 reply_id: 30715[/import]

If the compiler reads,

“…: replacing invalid existing signature
/…: signed bundle with Mach-O universal (armv6 armv7) […]
2011-04-02 09:59:06.236 Validation[1865:903] *** Warning: Defaulting to the standard codesign tool”

Is that a sure sign something is wrong? If so, what is it?

Nick [import]uid: 7472 topic_id: 8442 reply_id: 35095[/import]