ITMS-4238: Redundant Binary Upload. You've already uploaded a build with build number 'x' for version number 'y'
The build number (CFBundleVersion) has already been used for that version in App Store Connect.
Seen on:
iOS
Meaning
Each upload needs a unique, increasing build number per version. CI should set it automatically (agvtool or CURRENT_PROJECT_VERSION from the run number).
Common causes
- Build number not incremented
- Re-uploading the same archive
- Two pipelines using the same number
⚡ Quick fix
- Increment CURRENT_PROJECT_VERSION
- Automate it in CI
- Check existing builds in TestFlight
Detailed fix by platform
Shell
- swift
agvtool new-version -all $GITHUB_RUN_NUMBER # or: xcodebuild ... CURRENT_PROJECT_VERSION=$GITHUB_RUN_NUMBER
How to diagnose
- Number — Used before?
- CI — Auto-increment?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Command CodeSign failed Command CodeSign failed with a nonzero exit code (errSecInternalComponent / resource fork, Finder information not allowed)
- ITMS-90206 ITMS-90206: Invalid Bundle. The bundle at 'App.appex' contains disallowed file 'Frameworks'
- ITMS-90683 ITMS-90683: Missing purpose string in Info.plist (NSCameraUsageDescription etc.)
Most viewed in iOS
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026