Go to main content Go to main navigation Go to footer
Back to overview

Apple requires the iOS 26 SDK for new app builds starting April 28.

On April 28, 2026, a new Apple requirement went into effect for all apps submitted via App Store Connect. Starting April 28, 2026, apps and games uploaded to App Store Connect must meet minimum requirements: iOS and iPadOS apps must be built using the iOS 26 or iPadOS 26 SDK or later, tvOS apps using the tvOS 26 SDK or later, and visionOS apps using the visionOS 26 SDK or later.

Important: This applies only to new builds that you upload. Existing apps already in the App Store will remain available to your users, even if they were built using an older SDK. The requirement only takes effect when you submit a new version. The SDK (Software Development Kit) is the collection of tools, libraries, and APIs used to build an app that runs on a specific operating system. If your build is still configured for an older SDK version, Apple will reject your submission.

Joost van Dijk
Author Tech Lead | Team Pentagon
Reading time
5 min
Image without description

What this means for Flutter, React Native, and Swift.

For organizations that have mobile apps developed using Flutter, React Native or native Swift, this is a concrete requirement as soon as you want to release a new version. In practice, this means you must run your build on the latest Xcode version. For Expo projects, this means you will likely need to use the latest Expo version, as Expo’s build servers automatically use the current Xcode version.

Flutter projects that have not yet been updated to a version that supports the iOS 26 SDK can no longer be published or updated on the App Store. The transition from CocoaPods to Swift Package Manager is still ongoing. Apple strongly urges plugin authors to adopt Swift Package Manager, as it is now the standard for the Apple ecosystem. CocoaPods is the older package management system for iOS libraries; Swift Package Manager is its successor, which is seamlessly integrated into Xcode and better aligns with modern Apple standards.

Anyone using Flutter should also be aware of a related iOS lifecycle requirement: Flutter now supports the UIScene lifecycle by default, which is important for future iOS versions. This update is crucial for meeting Apple’s requirements for upcoming iOS versions. The UIScene lifecycle is how iOS handles multiple windows and app instances on a single device. If your app isn’t configured for this yet, it could lead to rejections during the review process or issues with future iOS updates.

What the consequences will be if you don't act now.

If you have an active iOS app in the App Store and you want to release a new version while your build isn’t yet configured for the iOS 26 SDK, that new version will be rejected immediately. Your existing app will remain available to users, but you will no longer be able to release security updates, bug fixes, or new features until you have resolved the technical issue. For organizations where the mobile app is a critical customer touchpoint, this can have immediate consequences for service delivery. The steps you need to take are as follows:

  • Upgrade to Xcode 26 (or the current Release Candidate)

  • Verify that your Flutter version supports the iOS 26 SDK and UIScene lifecycle

  • For Expo projects: update to the latest Expo version so that the build server uses the correct Xcode version

  • Migrate any iOS plugins from CocoaPods to Swift Package Manager

  • Test your build in a simulator environment before submitting

What Cube does for you.

Cube builds mobile apps using Flutter and React Native for the Dutch B2B market. If your app was already built by Cube, we ensure that SDK migration and platform updates are implemented on time as soon as you want to release a new version. Do you have an app built by another party and are you now facing this obstacle? Then Cube can quickly help you move forward, from technical analysis to a working build for App Store Connect.

Image without description

Please contact us before your submission is rejected.

Are you facing a rejection from Apple, or are you unsure whether your current build meets the iOS 26 SDK requirements? Contact us for a quick technical review and a plan of action.

Worth reading next...