Skip to content
Technical note· 7 min read
Published: Updated:

The Xcode 26 and iOS 26 SDK requirement: What you need to upload an update

Since April 28, 2026, apps uploaded to App Store Connect must be built with the 26 SDKs. Which Xcode and macOS versions you need, and where Expo and other cross-platform tools stand.

Short answer

Since April 28, 2026, iOS and iPadOS apps uploaded to App Store Connect must be built with the iOS 26 and iPadOS 26 SDK or later; these SDKs ship with Xcode 26. Xcode 26–26.3 needs macOS Sequoia 15.6, and Xcode 26.4 or later needs macOS Tahoe 26.2. Apple will require the 27 SDKs starting April 2027.

Free toolApp Store and Google Play deadlines

According to Apple's February 3, 2026 announcement, apps uploaded to App Store Connect since April 28, 2026 must be built with the 26 SDKs. That date has passed: today you cannot upload an update built with an older Xcode. Even for a small bug fix, you first need to update Xcode, and often macOS as well.

Requirements

RequirementValueNote
Start dateApril 28, 2026New apps and updates
iOS and iPadOSiOS 26 and iPadOS 26 SDK or later26 SDKs for tvOS, visionOS and watchOS too
Xcode 26 – 26.3macOS Sequoia 15.6 or lateriOS 26 – 26.2 SDK
Xcode 26.4 and latermacOS Tahoe 26.2 or lateriOS 26.4 and 26.5 SDK
Next stepApril 2027iOS 27 and the other 27 SDKs become mandatory

You can find Apple's and Google's other deadlines in one table in the app store deadlines tool.

Who does it affect?

  • Teams that ship updates regularly: if you already moved to Xcode 26, there is nothing extra to do.
  • Apps that haven't shipped an update in a long time: the next upload requires Xcode 26. If your Mac can't run macOS Sequoia 15.6, you have to solve the hardware problem first.
  • Cross-platform apps: React Native, Expo, Flutter and Capacitor projects are also built with Xcode on iOS; the same rule applies.

The rule covers new uploads only. Apple's announcement does not say that versions already live on the App Store will be removed.

What changes when you build with Xcode 26?

Liquid Glass: according to Apple's documentation, apps that use standard components from SwiftUI, UIKit or AppKit pick up the new Liquid Glass look when built with the latest SDKs. Bars, sheets, popovers and controls adopt the material automatically.

So after building, check the navigation bar, tab bar and buttons on a real device. If something no longer fits your brand, adjust the design.

Age rating questions: on July 24, 2025, Apple added new required questions to the age rating questionnaire and asked developers to answer them by January 31, 2026. If you haven't, you may hit an interruption when submitting updates.

Common upload problems

Undeclared required reason API (privacy manifest): according to Apple's documentation, since May 1, 2024, App Store Connect does not accept apps that don't describe their use of required reason APIs in their privacy manifest file. The rule covers third-party SDKs in your app as well as your own code.

The email you get after uploading may show a code such as ITMS-91053; Apple does not publish a list of these codes in its official documentation. You can use the privacy manifest generator to prepare the file.

Missing or vague permission text: permissions such as camera, location and microphone need a purpose string in Info.plist. Review Guideline 5.1.1(ii) requires these strings to describe your use of the data clearly and completely.

Non-public APIs: Review Guideline 2.5.1 says apps may only use public APIs. If an old third-party library trips this, update or replace it.

What to do

  1. Check your Mac's macOS version and install the matching Xcode 26 release from the table.
  2. Open the project, build it and note the warnings.
  3. Move CocoaPods or Swift Package Manager dependencies to current versions.
  4. Open the app on a device running iOS 26 and check the interface.
  5. Make sure the age rating questionnaire in App Store Connect is up to date.
  6. Upload to TestFlight; if everything works, submit for review.

Google Play has a similar rule on the Android side: the API 36 requirement.

Cross-platform tools

Expo: according to Expo's official post, projects on SDK 54 or 55 need no action; the default EAS Build image for those SDKs uses Xcode 26. On SDK 53 or older, you can switch to Xcode 26 by setting the image to "latest" in eas.json. Because compatibility depends on your dependencies, Expo recommends upgrading to at least SDK 54.

json
{
  "build": {
    "production": {
      "ios": { "image": "latest" }
    }
  }
}

Flutter: Flutter's official supported platforms page lists iOS 15–27 as supported and iOS 18 and 26 as CI tested. It does not publish a separate "minimum Flutter version" for Xcode 26; build and test with the current stable release.

React Native and Capacitor: we found no official minimum version for this rule. Building the project with Xcode 26 and testing it on TestFlight is the most reliable check.

In every case, updating the framework alone may not be enough; check every package that includes native code. If you'd like us to handle the update, see our React Native app development service.

Frequently asked questions

If I don't ship an update, will my app be removed from the App Store? Apple's February 3, 2026 announcement only sets the minimum SDK for new uploads; it says nothing about removing live versions. But you can't ship your next update without Xcode 26.

Will Xcode 26 run on my old Mac? Xcode 26–26.3 needs macOS Sequoia 15.6, and Xcode 26.4 or later needs macOS Tahoe 26.2. If your Mac can't run these, you need a cloud build service (such as EAS Build) or a newer Mac.

Do I need to change my minimum iOS version (deployment target)? This rule is about the SDK used to build, not the oldest iOS version your app supports. Apple's separate deployment target requirements are listed in the app store deadlines tool.

Sources

#güncel#ios#app store

Have a project in mind?

A short description is enough; if it isn't clear yet, we can think it through together. We'll write back within one business day.

With your consent, we use analytics cookies to improve the site and measure visits. Cookie policy