Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Apple will not take my app update because it was built with an old Xcode

Short answer

Apple publishes minimum Xcode and SDK versions for apps uploaded to App Store Connect, and it raises them over time. A build made with an older Xcode is refused at upload. The fix is building with a current Xcode, which on an old project can mean updating code and libraries first.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The upload fails with a message about the SDK or the Xcode version.
  • My developer's Mac is too old to run the Xcode Apple now asks for.
  • The project builds only with an old Xcode, and the new one shows errors.
  • The app has not been updated for a long time and the last build machine is gone.
  • A deadline email from Apple mentioned a new SDK requirement.

Why does this happen?

  1. Apple sets minimum Xcode and SDK versions for uploads

    Apple's upcoming requirements page lists, by date, which Xcode and SDK versions apps must be built with to be uploaded to App Store Connect. Older entries stay on the page, which shows that the minimum rises repeatedly.

  2. Each upload type has its own supported versions

    Apple's guide to uploading builds lists which Xcode versions are supported for building and uploading each kind of app, so a build can be produced correctly and still be uploaded with an unsupported tool.

  3. A new Xcode needs a Mac that can run it

    A newer Xcode normally needs a newer macOS, and sometimes a newer Mac. A developer on an old machine can be blocked before touching the code.

  4. The old project does not compile with the new tools

    A project last built years ago may use libraries, plugins or settings that the new Xcode rejects. Moving to the new tools means updating them first, which is a larger job than the upload.

  5. Deployment target requirements move too

    The same requirements page also lists a separate rule on the minimum iOS version an uploaded app must target, so an app that supports very old iPhones can hit a second requirement.

What can I do about it today?

  1. Read Apple's message to the endCopy the full error or email and send it to your developer. The exact version named in it is what they need.
  2. Open Apple's requirements pageSearch for Apple's upcoming requirements page and read the current minimum. It is written for owners as well as developers.
  3. Ask which Mac builds your appFind out whether it is the developer's own laptop, an office machine or a cloud build service, and what macOS it runs.
  4. Do not install tools on the owner's account to try itNever sign in to your Apple account on an unknown machine. The developer needs a role in the account, not your password.
  5. Plan a small releaseBecause the tooling change is large, ship only what you must and move new features to the release after.

When should I bring someone in?

  • The project does not compile with the current Xcode and the original developer is gone.
  • The app depends on libraries that are no longer maintained.
  • A required update is blocked and you have no working build machine.

How do I handle it?

  1. Check the exact requirementI read Apple's current requirement and compare it with the Xcode and SDK version the project uses.
  2. Build in a clean, current environmentThe project is built on a machine or build service with the required Xcode, and every error is listed before anything is changed.
  3. Update the minimum neededLibraries, plugins and settings are updated in the order the errors demand, and the app is tested after each step on real devices.
  4. Document the buildI write down the Xcode version, the steps and the signing setup, so the next requirement change is a known task.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Do I have to rebuild the app from scratch?

Not necessarily. Often the project is updated so that it builds with the new tools. Whether that is enough depends on how old the code and libraries are.

Will customers lose the app while this is fixed?

The version already on the App Store stays available. The requirement stops new uploads.

Does this affect Android too?

Google Play has its own rules, such as the target API level requirement, covered separately.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.