Apple mandates iOS 26 SDK and Xcode 26 for App Store submissions
Apple requires apps uploaded after April 28, 2026 to be built with the iOS 26 SDK and Xcode 26, a change that forces developers to update toolchains and may alter app UI defaults.

Apple told developers via its Developer News portal that uploads to App Store Connect will need to be built with the iOS 26 and iPadOS 26 SDKs, and matching platform SDKs for tvOS, visionOS, and watchOS, effective April 28, 2026. "Starting April 28, 2026, apps and games uploaded to App Store Connect need to meet the following minimum requirements:" the post said, creating a hard cutoff that in practice requires Xcode 26 or later for submissions. "In practice, this also means that developers will need to build their apps using Xcode 26 or later."
The change updates the minimum SDK used to compile App Store uploads; it does not force a higher runtime requirement for users. "On the other hand, this does not mean that apps will automatically require iOS 26 or later to run. This decision will still be up to the developer. This change affects only the SDK version used to build apps." That distinction matters for teams that must support older devices but need to adopt the new toolchain and SDK features.
Beyond the compilation rule, Apple’s guidance reiterates standard App Store expectations: submissions must be fully functional, not beta or placeholders, support 64-bit architectures, and provide demo credentials for reviewer access when login is required. Developers who distribute iPhone apps are reminded to make them run on iPad where feasible, and to keep privacy pages, App Privacy Labels, account-deletion flows, and AI transparency disclosures current. Apple also reminded teams: "Provide responses to the updated age rating questions for each of your apps by January 31, 2026, to avoid an interruption when submitting your app updates in App Store Connect."
One visible impact is appearance. "By default, apps built with the iOS 26 SDK apply the Liquid Glass look to native UI components, unless the developer explicitly takes steps to prevent that from happening." That means a build alone can change native controls and may require UI testing or opt-out work to preserve a previous look. At the time of reporting the latest iOS SDK was 26.2, so teams should test with the newest SDK patch before switching CI pipelines.

This annual cadence of SDK bumps is familiar to mobile developers. StackOverflow entries recall prior rollovers: "Starting April 2021, all iOS and iPadOS apps submitted to the App Store must be built with Xcode 12 and the iOS 14 SDK," wrote Harmeet Singh, and CennoxX noted the pattern: "The Xcode version changes once every year in April. Since April 2025 you need to built with the iOS 18 SDK and Xcode 16." Community commentary flagged operational risk: "It’s also worth noting that app stores tend to have a range of SDK versions that they will accept for new uploads... In some cases (such as with Google Play), app stores will even unpublish apps that were built with old versions of the SDK," wrote Hacker News user Sophira.
Practical next steps: update macOS and CI to support Xcode 26, run full UI and regression tests for Liquid Glass effects, update App Store Connect age-rating responses by Jan 31, 2026, and confirm third-party SDK compatibility. Remember the economics: Apple Developer accounts are $99/year (individual) or $299/year for enterprise distribution, and App Store commissions run 15–30% with a Small Business Program rate of 15% under $1M. Expect downstream patches from analytics, ads, and SDK vendors; plan builds and a staggered rollout so updates land before the April 28 deadline.
Know something we missed? Have a correction or additional information?
Submit a Tip

