Skip to content

App Store Connect upload errorApp Store Connect: “ITMS-90725: SDK version issue”

You upload a build and App Store Connect emails ITMS-90725: SDK version issue. Apple requires every upload to be built with a current Xcode and SDK, and this one was built with an older one, on your Mac or on a CI machine. The fix is the toolchain, not your code. Here’s the requirement in Apple’s words, or hand it over at a fixed price.

Short answer

Build with Xcode 26 or later, which uses the iOS 26 SDK. Check with xcodebuild -version on the machine that makes the build, and on Codemagic, GitHub Actions, Bitrise or EAS pick an image with Xcode 26. Then increase the build number and upload again. Plan for the next step too: Apple says uploads need the iOS 27 SDK starting April 2027.

Why the upload is refused, and the fix

  1. 01

    The build used an older Xcode

    “Apps uploaded to App Store Connect must be built with Xcode 26 or later using an SDK for iOS 26, iPadOS 26, tvOS 26, visionOS 26, or watchOS 26.” Apple, Upcoming Requirements

    The SDK comes with Xcode, so an older Xcode means an older SDK. Update Xcode on the Mac that archives the app, or select the newer one if several are installed.

    xcodebuild -version
    xcrun --sdk iphoneos --show-sdk-version
  2. 02

    The CI image is pinned to an old Xcode

    Cloud builds use the Xcode in their image. Change the image or Xcode version in your workflow file, run the build again, and check the Xcode version in the build log.

  3. 03

    Your framework needs a version that supports Xcode 26

    Flutter, React Native and Expo projects can fail to build on a new Xcode until the framework and its iOS dependencies are updated. Update them first, then build with Xcode 26.

  4. 04

    The iOS 27 SDK is next

    “iOS and iPadOS apps must be built with the iOS 27 & iPadOS 27 SDK or later” Apple, App Store submissions now open for the latest OS releases

    Apple has announced the next minimum. Moving to Xcode 26 now is required. Xcode 27 is already available, so you can test with it now and avoid the same email next spring.

Checked against the vendor’s docs on : Apple Developer: Upcoming Requirements; Apple Developer News: App Store submissions now open for the latest OS releases.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

Resubmit before Apple’s holiday slowdown

Pay for the Diagnosis and send the rejection and access to the app by (US Eastern). The Diagnosis is back by . Pay for the Fix that day and it arrives as a pull request by , in time to build and resubmit before .

In past years Apple said reviews may take longer around the holidays: December 20 to 26 in 2024 (opens in a new tab), December 22 to 27 in 2023 (opens in a new tab), December 23 to 27 in 2022 (opens in a new tab). Apple hasn’t posted its 2026 dates yet (checked ). Approval stays Apple’s decision.

Related: ITMS-91053 Missing API declaration · Xcode “requires a development team” · TestFlight Missing Compliance · ITMS-90725 in a Flutter app, step by step

Questions

More on this rejection

Do I have to raise the minimum iOS version too?

Not for this error. It is about the SDK the app is built with. Apple separately says iOS and iPadOS apps uploaded to App Store Connect must target iOS 13 or later. The blog guide linked below covers the April 2027 rules.

Is the build already in TestFlight affected?

Apple’s requirement is written for apps uploaded to App Store Connect, so the new upload is what gets refused. Build the next version with Xcode 26 to keep shipping updates.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.