Starting April 28, 2026, Apple requires every app and app update uploaded to App Store Connect to be built with Xcode 26 or later, using the iOS 26 SDK or the matching 26 SDKs for iPadOS, tvOS, visionOS, and watchOS. If you ship a Capacitor app, this is the deadline that matters.
The good news: for most teams, this is a build environment change, not a full app migration. And if you already use Capgo Build, your iOS build system is already on Xcode 26.
What Apple Changed
Apple published the requirement in its Upcoming Requirements page and repeats it on the App Store submission page.
Starting on April 28, 2026, App Store Connect no longer accepts uploads built with Xcode earlier than 26 or without the required 26 SDKs. Existing apps already live on the App Store keep working, but the next binary you submit must come from the new toolchain.
What It Means for Capacitor Teams
For most Capacitor apps, this is mainly about how you build the app, not about replacing Capacitor or rewriting your project.
Ensure every build path uses Xcode 26 or later:
- Local Mac builds: install and select Xcode 26 or later.
- Self-managed CI: use a macOS runner image with Xcode 26 or later.
- Native dependencies and older plugins: rebuild on the new SDK and test a fresh archive before your next release.
The failure mode here is simple: everything may still work in development, but App Store Connect will block the upload if the build came from an older Xcode line.
Capgo Build Is Already on Xcode 26
If you build with Capgo Build, you do not need to scramble to update your build environment for this Apple deadline. As of April 29, 2026, our current iOS build system is already running on Xcode 26 or later through Capgo Build.
That means teams using Capgo Build are already aligned with Apple’s April 28, 2026 submission requirement. No local Mac refresh, no runner image hunt, and no last-minute Xcode upgrade just to keep shipping.
When You Still Need to Act
You still need to make changes if any of these apply:
- You build and archive iOS apps locally and have not moved to Xcode 26 or later yet.
- Your self-managed CI pipeline is pinned to an older Xcode image than Xcode 26.
- One of your native SDKs or plugins has trouble when rebuilt with the iOS 26 SDK.
If that is your setup, update the toolchain first, then run a clean build and a TestFlight submission before planning a production release.
Final Take
This is Apple’s normal yearly toolchain cutoff, but the enforcement date is real: since April 28, 2026, older Xcode builds are no longer enough for App Store uploads.
If you use Capgo Build, you are already on Xcode 26 or later. If you build elsewhere, update your environment to Xcode 26 or later before your next iOS release.
