App Rejection Fix
App Store Medium Warning / notice

Invalid Binary: the upload was accepted, then failed validation

The archive uploaded and then the build turned to “Invalid Binary”, usually with an ITMS-90xxx email. Validation happens after upload, so the problem is in the binary itself — not in App Review.

Typical wording

Invalid Binary — We have discovered one or more issues with your recent delivery. Please correct the following issues and upload a new binary.

Common causes

  • The build was made with an SDK or Xcode version Apple no longer accepts
  • A required entitlement is missing, or an entitlement is claimed that the provisioning profile does not grant
  • Missing privacy manifest or required-reason API declarations for the app or a listed SDK
  • Unsupported or missing architectures, simulator slices left in a framework, or a bitcode-era artefact
  • Missing app icon at a required size, or an invalid Info.plist value (version, bundle ID, deployment target)
  • The version or build number is not higher than a build already uploaded

What to check

  • The ITMS email: it names the exact rule that failed
  • The Xcode Organizer validation step before distribution — it catches most of these locally
  • Toolchain: the app must be built with the current required Xcode and platform SDK
  • Entitlements versus the provisioning profile used for the archive
  • The privacy report generated from the archive (Xcode → Generate Privacy Report)

Fix, reply or appeal guidance

  • Fix the specific ITMS code rather than rebuilding blindly — each one maps to a single rule
  • Validate in Xcode Organizer before uploading; it is the same validation that runs server-side
  • Rebuild with the required Xcode and SDK version, then re-check entitlements and privacy manifests
  • Increment the build number for every upload attempt, even for a failed one

Read the detailed guide: iOS Code Signing & Profiles →