“xcode github”

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.

There are a couple of other threads on the OAuth issue. This morning I went into the Xcode components and uninstalled Claude Agent. Then I reinstalled it. SO FAR I haven't had a failed to authenticate, but it's too early to be sure.

I’ve managed to run the Xcode 26.4 debugger with an app on an old iPhone 5s running 12.5.8 (though it failed for a different reason). The trick was to install a developer disk image for iOS 12.4. Since Xcode does not grab it from the old iPhone I found it on GitHub where someone collected these old images. You need to copy the dmg and signature to /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport . Good luck.

It seems to be the same problem where the App Review automated system hasn't been updated to accept the new entitlements even though Xcode 26.4 has been out for more than a week now. I've raised FB22387339 for this. It actually was fixed, but then a different change reintroduced the same failure (r.173858947). It may take a day or two, but this should be sorted out soon. __ Kevin Elliott DTS Engineer, CoreOS/Hardware

+1, this gave me a hard time when prewarming Xcode on our dedicated CI machines. Same symptoms, xcrun simctl unresponsive, Xcode showing unavailable status, hanged in overall. I can't really recall this happening ever before. 🤨

Hello, Can we have an update on the progress ? It's been several months, we're now at Xcode 26.5, and still no fix in sight for this issue. We are still stuck on Xcode 16 for any kind of device debugging and we are not alone...