ContentDelivery 409 “corrupted binaries”

Builds rejected with generic ContentDelivery 409 “corrupted binaries” (no email, no Activity entry)

  • App ID: 6752832930
  • Bundle ID: com.taleway.tw
  • Toolchain: Xcode 16.0 (build 24319) on macOS 15.6.1 (24G90)

What happens

Archiving (Release, manual signing) succeeds. Upload/validation via Xcode Organizer or xcrun altool immediately fails with:

Validation failed (409) The app contains one or more corrupted binaries. Rebuild the app and resubmit. (ID: ef414ced-bf4e-40a6-8f5f-d4ba744c9433)

altool also reports a preceding 500 “internal server error” (L4JS7YJVZYJMHBI4ISC4L3UQBM) before the 409.

No system-generated email ever arrives (nothing under App Store Connect → Activity). We therefore have no specific error message or file name to fix.

What we’ve checked

  • Archive entitlements and embedded provisioning profiles match:
    • App entitlements: CarPlay audio, App Group group.com.taleway.tw, get-task-allow=false.
    • Intents extension entitlements: com.taleway.tw.TWIntents, get-task-allow=false.
    • Profiles decoded via openssl smime—entitlements align exactly.
  • No embedded frameworks at all; main binary is arm64 only (file TW).
  • No bitcode sections (otool -l shows no __LLVM segments).
  • No distribution Activity entries; case 102703979882 with Developer Support has bounced back twice with boilerplate “check your email”. The new

validation ID (ef414ced-bf4e-40a6-8f5f-d4ba744c9433) and 500 code are all we have.

Reproduction

  1. Archive TW scheme in Xcode (Release, manual signing).

  2. Upload via Organizer or:

    xcodebuild -exportArchive ... -exportPath /tmp/TWExport xcrun altool --validate-app -f /tmp/TWExport/TW.ipa -t ios
    -u <Apple ID> -p <app-specific password>

  3. altool output:

    ERROR: RETRIEVE UPLOAD OPERATIONS … internal server error (500) Validation failed (409) … (ID: ef414ced-bf4e-40a6-8f5f-d4ba744c9433)

Log bundle: /private/var/folders/.../TW_2025-09-23_23-21-30.952.xcdistributionlogs (happy to share privately).

Question

Can someone from Apple reveal the actual validation rule that’s failing for ef414ced-bf4e-40a6-8f5f-d4ba744c9433? I’m not getting the auto email, and Activity shows nothing. Looking to know whether this is the known Xcode 16 validator bug (arm64e/BrowserKit, bitcode, etc.) or if our archive is missing something.

Thanks!

• App Apple ID 6752832930, bundle id com.taleway.tw • Xcode Version 26.0 (17A324), macOS 15.6.1 • Validation IDs: da15f377-df62-456e-b876-323401f3b2b2, bb6f914d-3488-48dd-9cde-4e4eef9897eb, ef414ced-bf4e-40a6-8f5f-d4ba744c9433 • altool output showing the 500 and 409 • We never receive the promised email, nothing appears under App Store Connect → Activity • Archive entitlements/provisioning profile match (list the keys) • No embedded frameworks, arm64-only, no bitcode • Log bundle path: /private/var/.../TW_2025-09-23_23-21-30.952.xcdistributionlogs

ContentDelivery 409 “corrupted binaries”
 
 
Q