The iOS 26 SDK gate flipped on at 12:00 AM PT this morning. Anything you push to App Store Connect from now on has to be built with Xcode 26 against the iOS 26, iPadOS 26, tvOS 26, visionOS 26, or watchOS 26 SDKs — and watchOS has the new 64-bit slice on top of that. The first day of any Apple cutoff is always a small mess. This one is no different.
what's actually happening today#
The rejection isn't subtle. App Store Connect now responds to old-SDK uploads with a hard error at the binary validation stage, before the build even reaches the review queue. The SDK version embedded in your .ipa is checked against a minimum, and if it's lower, the upload gets rejected outright. No appeal flow. No "submit anyway" button.
The pattern I'm seeing across submissions today: it's not new builds that are failing. It's the metadata-only updates from devs who don't realise they still need a compliant binary in App Store Connect to push anything else. You can't change a screenshot, fix a typo in your description, or update an in-app event without an iOS 26 SDK build sitting there as the active version. People who treated last week's deadline as "don't ship a new version" are finding out today that it also means "don't change anything at all."
the watchOS bit that's biting#
The watchOS submissions getting rejected today are mostly companion apps that nobody actually changed — the parent iPhone app got a new build, but the watch target was still archived against the old SDK with 32-bit slices baked in. App Store Connect rejects the entire submission, not just the watch portion. If you have a watchOS companion you haven't touched in a year, today is the day you find out its ARCHS setting was customised to something that no longer compiles a 64-bit slice. Reset it to $(ARCHS_STANDARD) and rebuild.
the realistic next 72 hours#
If you missed the cutoff, you're not blocked from the store — your existing app keeps running. You're blocked from changing anything. The realistic timeline if you start today: 30 min to install Xcode 26 (it's a 14 GB download, start it before you read the rest), an hour to get a clean build, 30 min to opt out of Liquid Glass via UIDesignRequiresCompatibility = YES in Info.plist, then archive and upload. Add 24-48 hours of review queue time on top.
Don't try to also adopt Liquid Glass or the new SDK APIs in the same push. Get a compliant binary in first. Polish later.
the stora angle#
The compliance engine catches the SDK mismatch before you waste an upload slot — if the binary is wrong, the diagnostic is in your Stora dashboard in seconds instead of waiting on App Store Connect's slower validation pass. The build repair agent fixes the obvious cases automatically: stale ARCHS settings on watchOS targets, deployment targets that were quietly bumped by Xcode 26's project format upgrade, privacy manifests that drifted because a dependency added a new required-reason API.
It's not magic. You still have to install Xcode 26 and look at your app. But discovering the problem inside Stora before App Store Connect rejects you is meaningfully faster than the alternative.
closing#
Day one of any Apple cutoff is the day everyone finds out which assumptions about their own build settings were wrong. If you got rejected today, you're not behind — you're on the same page as half the indie devs who underestimated this one. Get the binary uploaded, then go read the Liquid Glass docs over the weekend.