Insights · 4 min read
Apple's 2026 SDK rule: why your iPhone app update gets rejected at upload
By Austin Hunter ·
Apple, like Google, moves the floor every year. This year's rule, from Apple's "upcoming requirements" page: apps uploaded to App Store Connect must be built with Xcode 26 or later, using the iOS 26 SDK (or the matching iPadOS, tvOS, visionOS or watchOS 26 SDK). It has applied to uploads since late April 2026.
What it does, and what it doesn't
- It controls the tools your app is built with, not which iPhones it supports. An app built with the iOS 26 SDK can still run on older iOS versions, if it's set up to.
- It applies when a new build is uploaded. Your current version stays on the App Store, but you can't ship a fix or a new feature until the app builds with the new tools.
- Builds made with older Xcode versions are refused at upload, before App Review ever sees them.
Why an old app can take real work
Moving to a new Xcode and SDK usually pulls in newer versions of the app's libraries and frameworks (React Native, Expo, Flutter or native dependencies), and those updates can break things that have nothing to do with Apple. An app that's been updated every year usually has a modest job ahead. One that's two or three versions behind can need a proper upgrade project first.
What to check
- Who has Account Holder or Admin access to your Apple Developer account and App Store Connect? If it's only a former developer, fix that first.
- When was the last build uploaded, and with which Xcode version?
- Do you have the current source code and signing setup?
- Are there other notices waiting in App Store Connect, such as privacy details or agreements to accept?
How we handle it
We keep our own apps current with Apple's SDK requirements every year, and our Care Plus plan includes this for client apps, with resubmission. If your app has fallen behind, we start with a short review and a fixed quote for bringing it up to date.