Help for owners
I uploaded my iPhone app and now App Store Connect says Invalid Binary
Short answer
Apple describes Invalid Binary as a build it received but that did not meet all upload requirements, so it does not appear for testing. A build that finishes processing with an issue shows Failed, and selecting it lists the errors. Fix the listed errors and upload again; the same build number can be reused after a failed upload.
Does this sound like your situation?
- The build never appears in TestFlight after the upload finished.
- App Store Connect shows Failed or Invalid Binary next to the build.
- I got an email after the upload, but it does not say what to do.
- The upload tool said Success, and yet there is no usable build.
- The build stays in Processing for a very long time.
Why does this happen?
Upload and processing are two separate steps
Apple says the build must be processed in its system before it appears in App Store Connect. A successful upload from the developer's computer only means the file arrived, not that it passed.
Confirmed by developer.apple.com
Failed means processing found a problem
In the build upload statuses, Failed means processing finished but the upload encountered an issue. Selecting the build shows the errors, warnings and information, and Apple says to resolve all errors before uploading again.
Confirmed by developer.apple.com
Invalid Binary means requirements were not met
Apple's build statuses page says Invalid Binary means the build was received but did not meet all upload requirements. The build is not visible in TestFlight for internal or external testing, and the fix is to resolve the issues and deliver it again.
Confirmed by developer.apple.com
The reason is often signing, version or required settings
Typical reasons are an expired or revoked signing certificate, an unsupported Xcode version, a missing description for a permission, or a missing privacy manifest. Apple's certificate page says builds signed with a revoked certificate may be marked Invalid Binary.
Confirmed by developer.apple.comTechnical detail: App Store upload rejected with ITMS-90683: missing purpose string for the camera
Processing can simply be slow
Apple says you receive an email when processing finishes and that a build still Processing after more than 24 hours may have a problem, in which case you can contact Apple.
Confirmed by developer.apple.com
What can I do about it today?
- Open the build in App Store ConnectAsk the person with access to select the failed build and copy every error and warning it lists. Send that text to your developer.
- Read the email as a notice onlyThe email tells you processing finished. Apple's page does not say that it explains a failure, so the errors in App Store Connect are the source of truth.
- Do not keep re-uploading the same fileThe same file gives the same error. Wait for the cause, then upload a fixed build.
- Check how long it has been processingIf a build is still Processing after a full day, say so when you contact the developer or Apple.
- Keep the live app untouchedA failed build never replaces the published version, so customers are not affected.
When should I bring someone in?
- The errors mention signing, certificates or profiles and nobody can read them.
- Every upload fails and the app has not been touched for a long time.
- A release date is close and the cause is still unknown.
How do I handle it?
- Read the error list, not the summaryI copy every error and warning from the build and sort them: signing, version, settings, privacy and library problems.
- Validate before uploadingApple's upload guide describes a validation step in its command line tool. I run it before each upload so problems appear on the Mac, not after a long wait.
- Fix the cause at its sourceA signing error goes to the certificate, a missing permission text goes to the app settings and a library error goes to its update.
- Upload and confirm CompleteThe target is a build that shows Complete and appears in TestFlight. Whether the app then passes review is Apple's decision.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is Invalid Binary the same as a review rejection?
No. It happens at upload processing, before the app goes to review. A review rejection arrives later with a reason from the review team.
Can I reuse the build number?
Apple's upload statuses page says that when an upload fails, you can reuse the same build number for the next upload.
Why did I get an email if it failed?
Apple's page says you get an email when processing finishes. It does not say what the email contains for a failure, so look at the build in App Store Connect.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
ITMS-90683: Missing purpose string in Info.plist.App Store upload rejected with ITMS-90683: missing purpose string for the cameraThe bundle's Info.plist does not contain a CFBundleVersion key or its value is not a stringInfo.plist has no CFBundleVersion, or its value is not a stringMissing private keyXcode shows a distribution certificate without its private key