Hi, Recently our App is facing a generic error with no error details. This error is happening once Build has been successfully uploaded to AppStore Connect through Xcode Organiser. Steps followed while uploading the build:
- Archive the Build through Xcode
- Once Archive is successful, Distributing the App through Xcode Organiser using AppStore Connect distribution method.
- Build Uploaded successfully to AppStore Connect
- After 5 min we are receiving a email with below message
Hello,
We noticed one or more issues with a recent delivery for the following app:
AppName App Apple ID 2121111 Version 3.6.9 Build 75 Please correct the following issues and upload a new binary to App Store Connect.
ITMS-90755: Invalid Binary - The following binaries in your app contains prohibited instructions: AppName.app/AppName. Remove the instructions from the binaries, rebuild and resubmit.
Apple Developer Relations
Solutions tried till now
- Updating Xcode to latest version of 16.4
- Recreating new Distribution certificates and Provisioning Profiles
- Clearing DerivedData and cleaning Build Folder
This issue seems to be occurring recently only since launch of Xcode 16.4
Other Device info Macbook Pro macOS: Sequoia 15.5 Xcode: 16.4
DTS has seen this ITMS-90755 error before and our general advice is:
- Check your project for build settings that enable non-standard instructions [1].
- If that doesn’t turn up anything relevant, the next step is to file a bug. However, I have some very specific advice in this front.
I believe that you’re currently submitting your app to App Store Connect using the Xcode organiser window. That’s fine in general, but for this task I’m gonna suggest a tweak:
- In Xcode organiser, select the problematic Xcode archive.
- Click Distribute App and follow the Custom > App Store Connect > Export workflow.
- In that workflow, select the same signing options you normally select.
- That’ll export an archive, either a
.ipafor iOS and friends or a.pkgfor macOS. Find that archive. - Use the Transporter app to upload that archive to App Store Connect.
That should reproduce the problem; if it doesn’t, lemme know and I can zen on this some more.
Assuming it does, file your bug with the details of the issue and attach the archive that you uploaded in step 5, the log that Transporter generated, and a copy of whatever error you got back from App Store Connect.
Once you’re done, post your bug number, just for the record.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] For example, a few years back we saw a developer hit this because they’d set a compiler flag that enabled AMX instructions on their Intel binary. But that’s just an example. When you start digging into the guts of a tool like Clang, you’ll find a whole world of weird and wacky code generation options.
