[UPDATE] It appears these two issues have been fixed on Apple’s servers.
Quick update on the “Apple App Submission Madness”…
Yesterday, Apple introduced (at least) 2 new issues that are affecting iOS devs (not just Corona devs), resulting in errors during app upload/submission:
[A] ERROR ITMS-9000: "Missing or invalid signature. The bundle ‘com.coronalabs.CoronaResources’ at bundle path ‘MYAPP.app/CoronaResources.bundle’ is not signed using an Apple submission certificate."
http://stackoverflow.com/questions/25755142/appstore-submission-missing-or-invalid-signature-com-google-gppsignin3presou
https://devforums.apple.com/message/1037466#1037466
There are numerous 3rd party SDKs that use resource bundles (no binaries). Presumably, this is related to extension support in iOS8, but it’s clear this is a bug in the iTunes Connect/ApplicationLoader filter.
[B] "Invalid binary, the binary is missing architectures[arm64]"
http://stackoverflow.com/questions/25760261/invalid-binary-the-binary-is-missing-architecturesarm64
https://devforums.apple.com/message/1037937#1037937
https://devforums.apple.com/message/1037960#1037960
https://devforums.apple.com/message/1038654#1038654
https://devforums.apple.com/message/1038407#1038407
Apple has not stated they require a 64-bit slice so this issue seems like a bug in the iTunes Connect/ApplicationLoader filter.
Several of the folks on the above url’s have filed reports to Apple. We have followed up with Apple as well, as this will help get more attention on these issues.
As with the previous false positive issue, you can help here too. The more folks tell Apple about the issue, the faster this can get resolved.
So, please choose from the letter below that corresponds to one of the above 2 issues, and send it to appreview@apple.com — don’t forget to fill in your ‘NINE_DIGIT_ID’ app id.
[ISSUE A]
SUBJECT: iTunesConnect bug: Resource bundles should not require signing
MESSAGE BODY:
Hi, our app binary (NINE_DIGIT_ID) cannot be uploaded to iTunesConnect b/c ApplicationLoader is *incorrectly* requiring resource bundles (no binaries) to be signed.
There are numerous 3rd party SDKs that use resource bundles (no binaries) including the Facebook Connect SDK. Presumably, this is related to extension support in iOS8, but the iTunes Connect/ApplicationLoader filter should be more intelligent about distinguishing between bundles with binaries and those that do not.
Currently there is no way to submit apps that use resource bundles. In addition, attempts to perform deep signing have failed: https://devforums.apple.com/message/1037466
Our app uses the Corona SDK engine. Corona incorporates several 3rd party frameworks/services that use resource bundles.
At least one radar bug has been publicly filed. rdar://18286739
sincerely,
XXX
[ISSUE B]
SUBJECT: iTunesConnect bug: 64-bit slices should not be required
MESSAGE BODY:
Hi, our app binary (NINE_DIGIT_ID) cannot be uploaded to iTunesConnect b/c ApplicationLoader is *incorrectly* requiring 64-bit slices.
Currently, Apple requires 64-bit apps to run well in 32-bit runtimes (https://developer.apple.com/library/ios/documentation/General/Conceptual/CocoaTouch64BitGuide/ConvertingYourAppto64-Bit/ConvertingYourAppto64-Bit.html)
However, the converse is not true. In other words, 32-bit apps are not required to offer 64-bit support. This is causing serious confusion in the developer community, as Apple did not state 64-bit slices as a requirement at this year’s WWDC:
* http://stackoverflow.com/questions/25760261/invalid-binary-the-binary-is-missing-architecturesarm64
* https://devforums.apple.com/message/1037937#1037937
* https://devforums.apple.com/message/1037960#1037960
* https://devforums.apple.com/message/1038654#1038654
* https://devforums.apple.com/message/1038407#1038407
At least one radar bug has been publicly filed. rdar://18290015
sincerely,
XXX