App Store Connect rejects the upload because the iOS SDK is too old
SDK Version IssueShort answer
App Store Connect accepts uploads only from builds made with the SDK version Apple currently requires. Since 28 April 2026 that is Xcode 26 or later with the iOS 26 SDK. Check which Xcode your Mac or CI machine uses, install a current Xcode and select it with xcode-select, then rebuild.
Fix it fast
1Find out which cause you have
Print the Xcode version that builds your app, and the path that xcode-select points at.
xcodebuild -version xcode-select -p2Match what you see, then jump to its fix
What does the error look like?
SDK Version Issue
Cause 1 of 2
The machine builds with an Xcode older than 26
1Check
Apple's upcoming-requirements page says apps uploaded to App Store Connect must be built with Xcode 26 or later, using the iOS 26 SDK (iPadOS, tvOS, visionOS or watchOS 26 for those platforms).
xcodebuild -version2Fix
Update Xcode the same way you installed it. The Flutter iOS setup guide says to update an existing Xcode with the original installation method.
# Update Xcode from the App Store or from developer.apple.com, then:
xcodebuild -version3Verify
The command now prints Xcode 26 or newer.
xcodebuild -versionConfirmed by developer.apple.com
Cause 2 of 2
A newer Xcode is installed, but another one is selected
1Check
xcodebuild and Flutter use the Xcode that xcode-select points to, not the newest one on disk.
xcode-select -p
ls /Applications | grep -i xcode2Fix
Point xcode-select at the new install and run its first-launch step, as in the Flutter iOS setup guide. Replace the path if Xcode is somewhere else.
sudo sh -c 'xcode-select -s /Applications/Xcode.app/Contents/Developer && xcodebuild -runFirstLaunch'3Verify
Build and archive again, then upload the new IPA.
flutter clean
flutter build ipaConfirmed by docs.flutter.dev
How do I stop it coming back?
- Read Apple's upcoming requirements page before each spring release, since the required Xcode version changes each year.
- Keep the build machine's Xcode in step with your development machine, and print xcodebuild -version in every build log.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- Dispatch ProA real-time logistics platform: Flutter apps, Spring Boot services and a Kafka event pipeline on AWS.
- Qist BazaarA buy-now-pay-later marketplace built from a blank repo, now past 100K downloads on Google Play.
Related fixes
Mobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
pod install cannot pick a version of a pod that satisfies every requirement
Specs satisfying the `FirebaseAuth (~> 11.0)` dependency were found, but they required a higher minimum deployment target.
CocoaPods tried every version of the named pod and none fit all requirements.
4 causes, each with a fixMobile apps
flutter run says: Could not run Runner.app, try Xcode Product > Run
Try launching Xcode and selecting "Product > Run" to fix the problem:
Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason.
4 causes, each with a fixMobile apps
flutter doctor says CocoaPods is installed but not working
You appear to have CocoaPods installed but it is not working.
Flutter runs pod --version and treats a failed or unreadable result as a broken install.
3 causes, each with a fixMobile apps
flutter run on iOS or macOS stops with Error running pod install
Warning: CocoaPods not installed. Skipping pod install.
Flutter only reports that pod install failed; the reason is in the lines just above it.
5 causes, each with a fixMobile apps
FirebaseMessaging.getAPNSToken() returns null on iOS
FirebaseMessaging.instance.getAPNSToken() returns null
getAPNSToken() gives null when iOS has not handed the app an APNs token yet or never will.
4 causes, each with a fix