Invalid Binary state after submitting to Review.

Hello,
I am trying to submit my new application to code review in Appstore.

  • I validate binary in XCode. OK.

  • I uploaded it from XCode to Appstore. OK. Completed processing.

  • I run it through TestFlight and tested on several devices. OK.

I submitted it to review.

  1. I got message. Waiting to Review.

  2. One minute later, I got Invalid bimary.

I tried one more time, and I created new build and and uploaded it. The same result.

I got mail from Apple - that application is in Invalid binary state. No explanation, no clarification...

OK, may be y Xcode installation is broken? I asked my team mate to build new release and upload it to Appstore. The same result, one minute after submitting to Appstore, I got message - Invalid binary. No clarification, no explanation.

I asked tech support. I got response - you should get message with explanation, make fixes and resubmit. I resend them message from Apple server. And didn't get any response from tech support at all.

I created another request. And put there reference to my previous request. And I got another common words as answer - something is wrong with your application...

I suspect, tech support doesn't read my mail at all...

So my question is: how can I get info, what actually is wrong with my application? Why Apple server considers it as Invalid, while all tests, I can make, returns me "Passed" state

Thanks in advance.

Regards,
Vladimir

Post not yet marked as solved Up vote post of VladimirVodolazkiy Down vote post of VladimirVodolazkiy
5.4k views
Posted by
VladimirVodolazkiy
Reply

  • Exact same issue, usecase: react native app Please let us know if nay update.

    —
    ashutosh_ornaz
Add a Comment

Replies

We have the exact same issue with an app update. We tried both Xcode 12.5.1 and Xcode 13.0 RC. It processes fine, and after submitting for App Store review, it goes into "Invalid Binary" state after exactly one minute each time. No details why or what's wrong with the binary.

Posted by
Schoenig
Post not yet marked as solved Up vote reply of Schoenig Down vote reply of Schoenig
Add a Comment

In my case solution was found after month or so discussing with several guys from the tech support. Problem was in the project itself.

I set on Maps support in the Signing & Capabilities, but no Routing mode was set, and no Routing area was provided in the AppStore info. page. As soon I removed this entry from the XCode project (as I do not provide route info in release version), error was gone.

So my advice is just check for something non-obvious and exclude any features from the project, which are not used.

Posted by
VladimirVodolazkiy
Post not yet marked as solved Up vote reply of VladimirVodolazkiy Down vote reply of VladimirVodolazkiy

  • That was exactly the issue for us. Thank you so much, Vladimir!

    —
    Schoenig
Add a Comment

When adding Apple Pay you must add the following to your info.plist on the Apple Side regardless if you plan on implementing scanning of credit cards I believe.

<key>NSPhotoLibraryAddUsageDescription</key> <string>Save Photos To Camera Roll</string> <key>NSCameraUsageDescription</key> <string>This app can use the camera to scan payment cards if you choose to use this feature.</string> <key>CADisableMinimumFrameDurationOnPhone</key>

If this is not added, an invalid binary issue will be reported when attempting to upload a build to testflight.

Posted by
ncamson
Up vote reply of ncamson Down vote reply of ncamson
Add a Comment