[RESOLVED] Apple/iOS App Submission Errors

Solar2D iOS
#61

I dont understand, i have done the same with the last version of my app and its giving me this error, you say the Problem A its resolved but im having the same issue, not a valid apple submission certificated…

i put the short string version, and all other stuff i created a lot of profiles to try it and the same error occurs… i need help because i have a big bugs in the online version that i want to resolved with this new one and on google play is updated but not in apple Store, i have 3 days doing everything and nothing happens!

best regards! 

#62

Ok, i delete everything and it’s working! thanks got sometimes apple Store makes me crazy!

#63

I solved my problem.

My client gave me a provisional profile with a certificate different of that i had permission.

I configure the provisional profile with certificate correct and work.

Thaks Rob!!!

#64

Submitted successfully by rebuilding with the same Corona 2393a and uploading separately with Application Loader 3.0! So disregard my post above.

#65

So what is the actual solution to the “not signed using an Apple Submission Certificate”? I have deleted all my profiles/certs and recreated everything trying to get this crapola working again.

Added this to my build settitngs.

CFBundleIconFile = “Icon.png”,

CFBundleShortVersionString = “1.0”,

CFBundleName = “Bumblebee Slot Machine”,

CFBundleDisplayName = “Bumblebee Slot Machine”,

CFBundleIdentifier = “slot.machine.bumblebee”,

This is driving me mad, I mean damn!!! 

I know my certs and provisioning profiles etc. that I just recreated are all fine, just tried a sample app with xcode and everything went just fine, just anything built with Corona gives me the apple submission certificate error.

Oh btw using latest build: 2014.2460

#66

@Christopher

I know this is probably a long-shot, but I’ve had a few times where my certificate issues get resolved by doing this.

Start Xcode. Select Xcode->Preferences and choose Accounts.

Select your Apple ID and click the “View Details” button.

Click the Refresh button in the lower left of the dialog sheet. Wait for it to complete… and click it…again.

This procedure seems to sometimes refresh things in a way Xcode likes. Maybe worth a shot unless you’ve already tried…

#67

@Ingemar,

Yeah already tried that was one of the first things I tried :slight_smile:

I have tried just about everything I can think of, so just cleaned up all my old certs, profiles etc. and currently format / re-installing a fresh copy of mavericks and see what happens with that lol…

This apple is only used for publishing with corona so re-installing isn’t that big of a deal :slight_smile:

The only thing I can think of at this point is there is something goofing with xcode/corona because I can use the exact same cert/profile via xcode with just a simple hello world build “from objective-c” not via corona and it works perfectly.

I did also try with IOS7/XCode 5 and the cert and profile worked fine via corona on that as well, it seems to only be happening on IOS8/XCode 6

#68

@Christopher

Yeah I thought you had most likely tried that already… Bummer…

Since I have Enterprise I always compile my Corona apps within Xcode. I’ll have a look at the app bundle that’s created by Corona and compare it with a native Xcode bundle and see if I spot anything unusual…

#69

Thanks :slight_smile:

I will also report back after this machine finishes its reinstall :slight_smile:

#70

Nope. I can’t find any weirdness in the app bundles between an Xcode and Corona build… :frowning:

#71

Ok now I am going to have to figure out what is really going on…

A fresh install of OSX and XCode resolved all issues with the exact same certs/profiles.

So I am going to have to compare the backup to current to figure this out as even know everything works now and can upload etc. and so forth it is still annoying me lol

#72

Great to hear that you got it working!

#73

Now I just got to figure out what was actually the problem lol, its going to keep bugging me :slight_smile:

#74

There are too many causes of this to say “That was the cause” as an answer for everyone.

I’ve seen an expired certificate/key pair in Keychain Access cause this even with a valid pair there.  You have to make sure to clean the Keychain Access out when you update your keys/certs.

I’ve seen people who put a bundleID in their build.settings forget that it’s there and then build against a different provisioning profile cause this.

I’ve seen people output their app build to their project folder.  I’ve seen people with folders named Res or Resources cause it.  Having an Icon on the OSX folder triggers that error.  Engineering has been working to harden up this block of causes.  Most of them should be addressed in the latest daily build.

Trying to make any edits to the Info.plist after the app is built will cause this error too.

Rob

#75

Ok, thanks for you work :slight_smile:

Kévin 

#76

Thank you for clarifying a lot about this, seems like many issues are coming up at this time.

#77

Got this error ITC.apps.assetvalidation.PURPLE_APP_FRAMEWORK_AND_APPEX_ARCHITECTURE_MISSING.error.message
when tried to submit an app.

#78

Just FYI:
I am getting the error: “Invalid Binary: missing architectures [arm64]” when uploading with Application Loader

#79

[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

#80

I just tested with latest build 2432

Issue A is resolved.

Issue B remains.