Invalid binary in Application Loader

Hi,

My previous attempt to get some help on this topic, failed, so I'm retrying again.


I've built my PhoneGap application without any problems until our Apple Development subscription expired (I guess, all the certificates expired as well).

While renewing our Apple dev program at our company, my boss made me a new account and added me as admin to the company.

I tried remaking the certificates, and while all my builds worked over at PhoneGap Build (means, that the certificates are valid), while trying to submit our app via the Application Loader, I get a binary error, and can't go any further.


Upon browsing the forums I've found out that this could be an issue with the certificates, so I came here to ask, what could be wrong with my setup.


I have to specify, that before this expiration happened, all our builds were submitted by using a Macbook, that is no longer available, so I can't access the old keychain information.


Also, another important information: while struggling with this issue, I remade all the certificates and profiles. (the App ID remains the same, since i don't need to change anything there)


Another note: our application supports push notifications, so I added that to the App ID, and created 2 certificates: Apple Development iOS Push Services and Apple Push Services. (I don't know if I need both, but I followed a tutorial, and it worked perfectly until the recent happenings)


We couldn't release our app for weeks now, which is a huge problem right now, so any help would be appreciated.

Accepted Answer

Well, since there was no support whatsoever, from the developer community, I gave it another shot, but this time I used XCode (which I never used before).

It turns out, the Application Loader that you can download from iTunes Connect when you create a new app or app-version, is outdated (version 3.0).

The one in XCode is version 3.6 as far as I remember.


Apple should update the standalone Application Loader to 3.6 or just simply remove it from the site.

Yep, same problem here with macOS Sierra and Xcode 8.2.1 and submitting an app to the Mac App Store.


Funny thing is, previous versions of the app, 1.0, 1.0.1, and 1.0.2 submission worked okay. Nothing has changed as far as entitlements, or code signing, or provisioning profiles. And yet, I am unable to submit 1.0.3 of my app. It gives me the unhlepful "Invalid Binary" message. And in one email:


App sandbox not enabled - The following executables must include the "com.apple.security.app-sandbox" entitlement with a Boolean value of true in the entitlements property list. Refer to the App Sandbox page for more information on sandboxing your app.


Which wasn't true, as the codesign command-line utility showed that the binary had the app-sandbox entitlement set to true.


I even went as far as revoking all previous certificates, and deleting all provisioning profiles, and regenerating from scratch. And turning off Xcode's automatic management of code-signing and ensuring release builds are using the production codesigning and provisioning profiles. Nothing.


Apple App Review suggested I open a Technical Support Incident, as they were unable to help, which I've done now. Still waiting.


Something appears to be seriously broken with Apple's app submission process viz. code-signing and provisioning profiles.

Invalid binary in Application Loader
 
 
Q