Did Apple change the minimum requirements for apps uploaded to App Store Connect?

Did Apple change the minimum requirements for apps uploaded to App Store Connect

Yes. Apple changed the minimum requirements for apps uploaded to App Store Connect, and the current rule is date specific: as of April 28, 2026, uploaded apps must meet Apple’s newer SDK requirements before they can move through review. Apple’s submission page and its requirements notice both say the change is in force now.

The part people get wrong is treating “uploaded” as the same thing as “approved.” It is not. App Store Connect accepts builds for processing, but Apple can still reject the binary later if it does not meet current requirements. Apple’s review status pages also separate upload, processing, and review outcomes, including the “Invalid Binary” state when a build does not meet current binary requirements.

The main change Apple lists is SDK minimums. For apps and games uploaded to App Store Connect, iOS and iPadOS apps now need to be built with the iOS 26 and iPadOS 26 SDK or later, tvOS apps need the tvOS 26 SDK or later, visionOS apps need the visionOS 26 SDK or later, and watchOS apps need the watchOS 26 SDK or later. Apple states this on both its submission page and its requirements notice.

That change matters even if your app still runs on older operating systems. Apple is not asking whether your app only targets new devices. It is asking what SDK you used to build the upload. A build can be technically functional and still fail Apple’s current upload gate if it was produced with an older toolchain.

Apple also updates other submission rules in App Store Connect, and those are easy to confuse with the SDK change. Its release notes now mention an App Review contact phone number format requirement in international format, and Apple’s submission flow keeps pointing developers back to the current App Review Guidelines and submission requirements. The minimum upload rule is one part of a larger set of submission checks, not the whole policy surface.

If you are preparing a release, the practical step is simple: open the project in a supported Xcode version, confirm the build uses the required SDK for that platform, then upload the binary and recheck App Store Connect for warnings before you submit for review. Apple’s build upload help explains that you can upload through Xcode, Transporter, or the App Store Connect API, but the binary still has to satisfy current platform rules.

The inconvenient part is that these changes do not stay static. Apple publishes upcoming requirements and then turns them into live minimums on a specific date. That means an app that uploaded cleanly before a cutoff can start failing later, without any code change in the app itself. The only safe habit is to check Apple’s current submission page before every release, not just when a build starts failing.

If your question is really about whether Apple changed the minimum requirements for “apps uploaded to App Store Connect,” the answer is yes, and the concrete change is the SDK requirement effective April 28, 2026. If you are also checking whether other submission details changed, Apple’s App Store Connect release notes and submission docs are the right place to verify the exact current rules for metadata, review contacts, and build acceptance.

For teams shipping often, the safest workflow is to treat App Store Connect as a moving target. Before release day, confirm three things: the Xcode version, the SDK version, and any metadata fields Apple recently tightened. That avoids the common failure mode where the app code is ready but the submission stalls on a rule that changed after the last release.

If you want to save a release cycle, check the current Apple submission page first, then rebuild from a toolchain that matches the active minimums. A clean compile is not enough when Apple has raised the bar for what can be uploaded.