“xcode github”

Distribution through the App Store requires a minimum deployment target of iOS 15. For future reference, you can find this information listed on the Xcode Support webpage.

@patrick Thanks for the post and providing a workaround, have you tried Xcode 26.5 beta without the workaround? Can you let me know if that works well for you? Anyone in this thread has filed a bug for this? If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Albert Pascual
  Worldwide Developer Relations.

I'm seeing exactly the same crash, same source code, same Xcode version two weeks ago did not have the issue. I've pushed a new build 2 days ago and users with iOS 12 are getting a crash on launch.

Let's just pile on here. Same issue. Unbearably bad and a productivity killer. Up to date OS on all devices. Spend half my day waiting for Xcode to reconnect to my watch that it was already connected to.

I have the same issue with Xcode 26.4 after installing macOS 26.4. What help is (do it at your own risk, no guarantee): Force quit Xcode rm /Library/Developer/CoreSimulator/Images/images.plist Wait 1-2 minutes Launch Xcode You will be able to download the Platform Support Components from Xcode again.

Here is more concrete context. Platform / tools Target: macOS app Language / frameworks: Swift, SwiftUI, SwiftData Cloud sync: SwiftData with CloudKit mirroring in the production configuration Xcode: 26.4 (17E192) Test OS: macOS 26.4 (25E246) What I’m seeing In the macOS app, issue board scrolling can become inconsistent or very slow. Changing an issue status from detail view can be very slow. Scrolling the status menu itself can be slow. Typing in issue description/notes fields can become sluggish. The problem is much more noticeable with my full production-sized dataset than with a small dev dataset. What I’ve tested so far I compared a small dev dataset vs a much larger production-sized dataset. With a small dataset, the same UI feels fast and smooth. With the large dataset, the same UI becomes noticeably slower. I also tested a local-only copy of the production dataset with CloudKit disabled. That improved some behavior, but it did not remove the lag entirely. When I reduced the local test datase

Thanks for bringing this to the forums. [quote='821286021, vpoinot, /thread/821286, /profile/vpoinot'] But would you be aware of a reason that would explain the delay observed by these customers? [/quote] No. And the fact that this only happens at specific sites makes it hard to offer useful insight. What I can do is suggest a path for investigating this. IMPORTANT I’m gonna assume you’re familiar with the system log. If not, read Your Friend the System Log. I’m also going to suggest an approach that’s kinda like the one I outlined in Using a Sysdiagnose Log to Debug a Hard-to-Reproduce Problem, so you might want to read that for more background. The canonical tool for investigating issues like this is a sysdiagnose log. In a case like this that’s only going to work if you have a customer who is reasonably technically savvy and willing to help you debug. A further complication is that NE content filter data providers can’t log to the system log when signed for distribution. They can only add stuff to the syst

We work hard to keep our application available to older devices, just to get the rug pulled from under our feet... Please restore the ability to launch on iOS 12: this was working perfectly well less than a month ago with Xcode 26...

Yep, seeing the same thing. There's a lot of other stuff broken with Xcode 26.4. For example, the Swift symbol NSTextAttachment.character is gone and we have to use NSAttachmentCharacter which in turn produces an error when compiling with Xcode 26.3 and earlier. (FB22341879). And then there's the broken Claude Agent support which forces you to re-login every few hours. Paired with the fact that macOS 26.4 cannot run Address Sanitizer builds from Xcode 26.3 and earlier, and you thus HAVE to use Xcode 26.4, I'm very frustrated with Apple's software quality right now.