App Store Connect Minimum SDK Requirements Update
Apple now requires apps uploaded to App Store Connect to be built with Xcode 26 or later and SDK 26 across its platforms starting April 28, 2026. Expo SDK 54 and 55 already align with this requirement, while projects on SDK 53 or earlier should verify build images and plan upgrades to remain eligible for submission.
Summary
Apple now requires apps uploaded to App Store Connect to be built with Xcode 26 or later and SDK 26 across its platforms starting April 28, 2026. Expo SDK 54 and 55 already align with this requirement, while projects on SDK 53 or earlier should verify build images and plan upgrades to remain eligible for submission.
Key Updates
- App Store Connect uploads must use Xcode 26+ starting April 28, 2026.
- SDK 26 is now the minimum across iOS, iPadOS, tvOS, visionOS, and watchOS.
- Expo SDK 54/55 are aligned; SDK 53 and earlier projects need build-pipeline review and likely upgrade planning.
Why It Matters
This is part of a consistent pattern: Apple is making SDK compliance a release-readiness issue, not an occasional maintenance task.
Teams that delay upgrades risk hitting submission blockers right before a planned release. For Expo and React Native workflows, this reinforces a practical operating model: stay within one or two SDK versions of latest, and treat toolchain compatibility as part of release velocity.
Builder Takeaway
Treat SDK alignment as part of your release pipeline, not a last-step check.
- If you’re on Expo SDK 54/55, validate your next iOS build once and move on.
- If you’re on SDK 53 or earlier, check your `eas.json` build image and plan the SDK upgrade before submission pressure.
- Add SDK/toolchain checks to CI or pre-release validation.
The risk is not just technical debt. It is blocked distribution.