Urgent fix needed: XCode 27.2 update does not allow distribution to app store (Unsupported SDK or Xcode version)

Hi there,

As the title says, distributing to the app store is currently not possible on the live XCode 27.2 update that was released 9 hours ago. ASC does not accept it as a distribution version:

Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases.

Best,
Beren

Answered by fabianlucas in 913672022

App Store upload with Xcode 27.2 (27B52) works now.

As of 14:45 UTC on Friday, October 30, 2026, this is still happening.

My duplicate report, with more detail, is here:

As of 14:45 UTC on Friday, October 30, 2026, this is still happening.

It's been happening for about 10 years now. People are just going to have to wait a couple of days.

I have replied to the other thread to check the App Store Release notes when a build of Xcode is allowed to the App Store as @Etresoft also explained.

Albert  WWDR

Don't use the comments. They hide your replies. Ideally, tag someone with @Bikrrr, to send out an e-mail notification.

I swear I’ve pushed builds soon after public Xcode releases before

I'm sure you have. But in most cases, I've seen very similar comments in similar venues.

Personally, I don't see why anyone would ever want to do that. Apple's been known to make last-minute changes in the past. These days, there are very significant changes in app behaviour based on Xcode version (via SDK version).

@Etresoft Yeah, I realize comments here are basically only seen by the person being "commented" to. Wish Apple would fix that, or just get rid of comments.

Regarding your question, the reason is to get past the bugs in the prior release (for me, Device Hub was constantly crashing or misbehaving). I intentionally skip Xcode betas and RCs to avoid headaches like this. I didn’t realize there was a delay between a public Xcode release and when its builds are accepted in the App Store.

It’s clearly not obvious, given the “me too” posts piling up on at least one Twitter thread I found.

Having to watch yet another page when you’re desperate for bug fixes pushes the onus onto thousands of app devs. A simple "App Store Connect" status on the Download page would fix that, possilby like this:

Having the same issue. Hope they get this fixed soon.

Dan Uff

Me too maving the same issue!!!

I realize comments here are basically only seen by the person being "commented" to.

Not even by them. I just know about the problem. I regularly check my previous posts to see if anyone has used a comment. That's the only way to tell.

Wish Apple would fix that, or just get rid of comments.

Agreed. I even double-checked preferences just know. I have all email notifications enabled. Comments don't trigger those.

But the new edit window is nice!

Regarding your question, the reason is to get past the bugs in the prior release (for me, Device Hub was constantly crashing or misbehaving). I intentionally skip Xcode betas and RCs to avoid headaches like this.

I skip a lot more than that. My primary development, and exclusive submission, machine is Sequoia with Xcode 26. And even that has caused problems. Use of the 26 SDK opted my app into Liquid Glass which, for whatever reason, made my toolbar items completely obscured on 26/27. Kinda the opposite of the intended effect. This is a legacy app anyway, so now I build on my older Ventura machine with whatever Xcode that is.

But this is not an App Store submission. When Apple tightens the screws in April next year, I'm going to need a separate machine just for App Store submissions. I'm happy to let all you folks work out the bugs for me.

I didn’t realize there was a delay between a public Xcode release and when its builds are accepted in the App Store.
It’s clearly not obvious, given the “me too” posts piling up on at least one Twitter thread I found.

It's actually an inconsistency. You can use late beta builds when submitting for a major new marketing version. But even then, there's a delay of a couple of day. People just accept it and forget it about. But it's the same delay.

Having to watch yet another page when you’re desperate for bug fixes pushes the onus onto thousands of app devs. A simple "App Store Connect" status on the Download page would fix that, possilby like this:

There's no way Apple could manage to do that.

App Store upload with Xcode 27.2 (27B52) works now.

@fabianlucas Thanks for letting us know

Albert  WWDR

Accepted Answer

FUTURE REFRENCE for someone having a smilar issue.

I solved this temorarially (needed to ship asap)

I went to this link and downloaded the previous version. Expanded the xip file and ran the older version. Archived and deployed. Worked fine.

https://developer.apple.com/download/all/

So to summarize: it took 19 hours after the public release of a new XCode version for it to be able to distribute to the app store. This is somehow considered acceptable?

It's like buying the new iPhone on release day trading in your old one but you can't do any calls on day 1. Emergency? Not today!

Seriously, this really should not happen and should not be considered acceptable 'because it happened before'.