--- title: Apple's New Xcode 26 Requirement for Capacitor Apps description: Apple now requires Capacitor apps to be built with Xcode 26 and the iOS 26 SDK. Here's what changed and how Capawesome Cloud handles it for you. date: created: 2026-04-29 updated: 2026-07-17 authors: - robingenz categories: - Capacitor - Cloud faq: true --- # Apple's New Xcode 26 Requirement for Capacitor Apps Yesterday, April 28, 2026, Apple's new SDK requirement went into effect. Every app submitted to App Store Connect now has to be built with Xcode 26 and the iOS 26 SDK (or the matching SDKs for iPadOS, tvOS, visionOS, and watchOS). If you're shipping a Capacitor app, here's what changed — and why most Capawesome Cloud customers don't need to lift a finger.
Build and deploy your Capacitor app with Capawesome Cloud
## What Apple Announced Apple shared the change in a [developer notice in February 2026](https://developer.apple.com/news/upcoming-requirements/?id=02032026a){:target="_blank"}. From April 28, 2026 onwards, any app or app update submitted to App Store Connect must be built with **Xcode 26 or later** using the SDKs for **iOS 26, iPadOS 26, tvOS 26, visionOS 26, or watchOS 26**. The previous baseline (Xcode 16 / iOS 18 SDK) is no longer accepted for new submissions. Apps already on the App Store keep working — but the next time you push an update, the build needs to be on the new toolchain. ## What This Means for Capacitor Developers Capacitor itself is fully compatible with Xcode 26 and the iOS 26 SDK, so there's no Capacitor-side migration involved. The change is about the toolchain you build with, not your app code: - If you build locally on a Mac, you need Xcode 26 installed and selected via `xcode-select`. - If you build in CI, your runner needs to provide Xcode 26 — many older CI images still default to Xcode 16. - If you let a service like Capawesome Cloud build for you, the build stack you pick determines your Xcode version. That last point is where most teams will spend the least effort. ## Capawesome Cloud Has You Covered Both [build stacks](../../cloud/native-builds/build-stacks.md) on Capawesome Cloud already ship Xcode 26 as the default: | Build stack | Default Xcode | | --------------- | ------------- | | `macos-sequoia` | 26.0.1 | | `macos-tahoe` | 26.2 | If you've never explicitly overridden `XCODE_VERSION` in your build environment, you're already compliant. Your next build will produce a binary that App Store Connect accepts. ## When You Need to Act There's exactly one case where action is required: you've pinned an older Xcode via the [`XCODE_VERSION` reserved environment variable](../../cloud/native-builds/environment-variables.md#reserved-variables). If your build environment still contains something like: ```bash XCODE_VERSION=16.4 ``` Either remove the variable to fall back to the default, or update it to a Xcode 26 release (`26.0.1` on `macos-sequoia`, `26.2` on `macos-tahoe`). Then trigger a fresh build — and you're done. ## FAQ ### Does an app already on the App Store stop working if it wasn't built with Xcode 26? No. Apps already live on the App Store keep working exactly as before — the requirement only applies the next time you submit a new build or update. There's no retroactive enforcement on binaries that already passed review. ### Do I need to change anything in my Capacitor app's code for this requirement? No. This is entirely a toolchain requirement, not a Capacitor compatibility issue — Capacitor itself is fully compatible with Xcode 26 and the iOS 26 SDK. The change is about which Xcode version compiles your app, not anything in your web or native project code. ### How do I know if my Capawesome Cloud builds are already compliant? If you've never explicitly set the `XCODE_VERSION` reserved environment variable in your build environment, you're already compliant, since both build stacks (`macos-sequoia` and `macos-tahoe`) default to Xcode 26 releases. Compliance only becomes a concern if you previously pinned an older version like `XCODE_VERSION=16.4`. ### What happens if I submit a build made with an older Xcode version after the deadline? Apple's stated policy is that submissions built with the older baseline (Xcode 16 / iOS 18 SDK) are no longer accepted from April 28, 2026 onwards — so a build made with an outdated toolchain would be rejected at submission rather than approved and flagged later. ### Is this a one-time requirement, or does Apple do this every year? Per this post, it's described as part of a routine annual cycle — Apple has a history of raising the minimum required Xcode/SDK version on a yearly cadence, tied to each year's new OS releases. That's also why keeping build stacks current is an ongoing effort rather than a single fix, as covered in [the new CLIs and Xcode 26 update](./new-clis-and-xcode-26-in-capawesome-build-stacks.md). ## Try Capawesome Cloud If you're still building Capacitor iOS apps on a local Mac and are tired of chasing Xcode upgrades every spring, Capawesome Cloud handles the toolchain for you — including future Apple deadlines like this one. [Try Capawesome Cloud Free](/){ .md-button .md-button--primary } ## Final Thoughts Apple's Xcode 26 requirement is part of a routine annual cycle, but it's the kind of deadline that's easy to miss until your next App Store submission gets rejected. With Capawesome Cloud's default build stacks, the upgrade is automatic. The only thing to double-check is whether you've pinned an older Xcode version somewhere in your environment. If you'd like to go fully Mac-free for your iOS builds, our guide on [how to build and deploy iOS apps without owning a Mac](./how-to-build-and-deploy-ios-apps-without-a-mac.md) walks through the full setup. We also keep the build stacks current over time — see [the new CLIs and Xcode 26 in the Capawesome build stacks](./new-clis-and-xcode-26-in-capawesome-build-stacks.md) for the latest Xcode defaults and tooling. Questions? Join us on the [Capawesome Discord server](https://discord.gg/VCXxSVjefW){:target="_blank"} or subscribe to the [Capawesome newsletter](/newsletter/){:target="_blank"} to stay ahead of the next Apple deadline.