After April 28, any App Store submission not built with iOS 26 SDK gets auto-rejected
Xcode 26 RC requires macOS Sequoia 15.6, which means CI runners need updates too
The new SDK applies Liquid Glass styling to native UI components by default
watchOS apps now require 64-bit support on top of the SDK bump
Update macOS, install Xcode 26, fix deprecations, update CI, and test on device before the deadline.
Apple just set a hard deadline that will catch unprepared teams off guard. Starting April 28, 2026, every app and game uploaded to App Store Connect must be built with the iOS 26 SDK using Xcode 26. No grace period. No exceptions. Miss it and your submission gets rejected.
This isn't just an iOS requirement. The same deadline hits iPadOS 26, tvOS 26, visionOS 26, and watchOS 26 simultaneously. If you ship on multiple Apple platforms, every target needs updating at the same time.
What Changes on April 28
The requirements are simple. The ripple effects are not.
Every App Store submission after April 28 must use Xcode 26 RC or later. That means macOS Sequoia 15.6 or later on your build machine. If your team builds on older macOS versions, you need hardware or VM updates before the code changes even start.
The SDK requirement is uniform across all platforms. iOS 26, iPadOS 26, tvOS 26, visionOS 26, and watchOS 26. No platform gets a later deadline. watchOS apps have an additional requirement: 64-bit support is now mandatory. If you've been shipping 32-bit watchOS binaries, that era is over.
One detail that will surprise developers who haven't tested with the new SDK yet: apps built with iOS 26 automatically get the Liquid Glass look applied to native UI components. This isn't optional. It's the new default. Unless you explicitly opt out in your code, your buttons, navigation bars, and tab bars will render with Apple's translucent glass styling. For apps with heavily customized UIs, this could break visual consistency across the entire interface.
This happens every year. The annual SDK deadline is a ritual at this point. But the Liquid Glass visual overhaul makes this cycle different from a routine SDK bump. You're not just updating compiler targets. You're inheriting an entirely new visual language that changes how your app looks without a single line of code from you.
That's the part most developers haven't processed yet.
Where Teams Get Stuck
The SDK update itself takes minutes. The fallout from it takes days.
Deprecation cascades. New SDKs surface API removals and deprecation warnings that have been accumulating for years. One developer described the experience well: a hotfix that should take an hour turns into a two-day project because the new SDK surfaces 47 deprecation warnings that all need attention before the build passes cleanly.
CI/CD infrastructure. This is the part that trips up the most teams. Your CI provider needs to offer macOS Sequoia 15.6+ runners with Xcode 26 pre-installed. GitHub Actions, CircleCI, Bitrise, and other providers roll out new images on their own timelines. If your runner image doesn't support macOS 15.6, your pipeline breaks regardless of how clean your code is.
Check your CI configuration now. Not the day before the deadline. Runner image updates can take days to propagate across all providers, and some require manual configuration changes. If you use self-hosted runners, you're responsible for the macOS and Xcode versions yourself. Hosted runners from major providers typically lag behind Apple's releases by a few weeks. That gap becomes a problem when your deadline is fixed.
For teams using Fastlane or custom build scripts, check your Xcode selection logic too. Scripts that hardcode Xcode paths or use xcode-select defaults will break silently if the wrong version is active during a build.
visionOS complications. If you ship a visionOS app, expect extra work. Apple has been iterating on spatial computing APIs aggressively since Vision Pro launched, and each SDK version introduces breaking changes that go beyond deprecation warnings. Spatial layout, interaction patterns, and rendering APIs have all shifted between versions. The visionOS developer base is still small enough that community fixes and workarounds are harder to find than on iOS.
Third-party dependencies. Every SDK you depend on also needs to compile with Xcode 26. One outdated dependency that hasn't been updated will block your entire build. Audit your Podfile, Package.swift, or Cartfile now. Check which dependencies have already shipped Xcode 26 compatible versions and which are still pending.
In my experience, the dependency audit takes longer than the actual code changes. Popular libraries update quickly. Niche SDKs maintained by one person can lag by months. If you find a critical dependency without Xcode 26 support, start looking for alternatives or forks now. Waiting until April 27 to discover a blocking dependency is the worst position to be in.
What Liquid Glass Means for Your UI
Liquid Glass isn't just a visual refresh. It's a behavior change that affects your app the moment you compile with the new SDK.
Liquid Glass is Apple's new design language that applies translucent, glass-like effects to standard UIKit and SwiftUI components. When you build with iOS 26 SDK, these effects apply automatically to system-provided controls. Navigation bars become translucent. Tab bars get the glass treatment. Buttons pick up new visual weight.
If your app uses standard components with minimal customization, the transition might look fine. If your app has a dark theme, custom navigation, or branded color schemes, Liquid Glass could clash with your existing design in ways that look unintentional to users.
The opt-out mechanism exists but requires explicit code changes per component. You can't flip a single switch to disable it globally. Each affected component needs individual attention.
Test your app's visual hierarchy with the new SDK before submitting. Screenshots in App Store Connect that show the old UI next to a Liquid Glass-styled app will look inconsistent. Users will notice.
As a designer, I actually like the direction Apple is going with Liquid Glass. The translucent layering creates depth without adding visual weight. But that's a design opinion. The engineering reality is that it introduces visual regressions in apps that weren't designed with translucency in mind. Dark-themed apps with solid backgrounds will suddenly have semi-transparent navigation elements floating over content. Custom color palettes that looked intentional will now compete with system-rendered glass effects.
The safest approach is to build with Xcode 26, screenshot every primary screen, and compare them side by side with your current production version. Flag anything where the new styling conflicts with your brand or makes text harder to read. Then decide screen by screen whether to adopt or opt out.
The Checklist Before April 28
Here's what to do in order, starting now:
Update macOS to Sequoia 15.6 or later on at least one build machine
Install Xcode 26 RC from the Apple Developer portal
Build your project and read every warning carefully. Treat deprecation warnings as blockers, not noise
Audit dependencies for Xcode 26 compatibility. File issues on packages that haven't updated
Update CI configuration with the correct runner image, Xcode version, and SDK flags
Test Liquid Glass on every screen. Decide where to accept the new look and where to opt out
Test on physical devices across all platforms you support
Submit to TestFlight before going to App Store. Catch rejection reasons early
The advice is the same every year: start the SDK migration the day Apple announces it, not the month it becomes mandatory. If you're reading this and haven't started, you have 15 days.
Bottom Line
Apple's April 28 SDK deadline is a hard cutoff with no extensions. The Xcode 26 requirement cascades into macOS updates, CI pipeline changes, dependency audits, and the Liquid Glass visual overhaul that affects every app using standard components.
The teams that started migrating in February are already submitting builds. The teams that start this week will be racing the clock. If you maintain a visionOS or watchOS app alongside iOS, multiply your timeline estimate by the number of platforms.
15 days. Update your build tools, fix your deprecations, test Liquid Glass on every screen, and submit to TestFlight before the deadline hits. Don't wait for the rejection email to find out what broke.
If you only do one thing today, install Xcode 26 RC and hit build on your project. The warning list will tell you exactly how much work is ahead. That number is your planning input for the next two weeks.
Top comments (0)