“Xcode”

Hi Quinn, I have an additional clarification about the logs from the target Mac, now that I’ve instrumented the code more precisely. On this machine I actually see two different behaviours for NEAppProxyUDPFlow.writeDatagrams: In the main DNS path (NEDNSProxyProvider → NEAppProxyUDPFlow → TCP upstream via SwiftNIO), writeDatagrams always fails with The datagram was too large, even for very small responses (for example 33, 50, 66, 67, 147, 193 bytes). The only writeDatagrams OK entries I see in the logs come from a separate passthrough handler that talks directly to a fallback DNS server (8.8.8.8) and uses a different code path. So, for the specific flow we are discussing (the proxy that forwards DNS over TCP to our upstream and then sends the response back to the client), writeDatagrams never succeeds on this Mac: every attempt ends with The datagram was too large, regardless of the actual payload size. This seems to match what you described about the subtle differences between endpoint type

[quote='882538022, AlexPan19920718, /thread/820969?answerId=882538022#882538022, /profile/AlexPan19920718'] FB: FB22384135 [/quote] Thanks for filing that. I took a look at Xcode 26.5b1 and it still seems to have the problem )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='882565022, nckh, /thread/820929?answerId=882565022#882565022, /profile/nckh'] Seems to be fixed in Xcode 26.5 beta 1 :) [/quote] Yay! Thanks for the heads up, and also for testing with Apple’s beta seeds. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to start by pointing you at TN3158 Resolving Xcode 15 device connection issues. This provides general background and one critical data point, namely, it shows how to identify the direct link interfaces used by Xcode. [quote='821229021, tathac, /thread/821229, /profile/tathac'] I have my web content filter … and there is also SentinelOne web content filter with same configuration. [/quote] I’m presuming that this SentinelOne filter isn’t something you have direct control over. Given that, my advice is that you remove it from the equation and replace it with a placeholder content filter that you do control. This gives you full control over the (non-Apple) bits of the stack. That’ll tell you whether this issue is fundamental to having two content filters installed, or whether there’s something specific about the SentinelOne filter that’s triggering the issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

For me, the issue is NOT resolved in Xcode 26.5 beta. I downloaded it and created a 26.5 simulator, but I can NOT paste into it from macOS 26.4 host.

I've hit a very similar issue with CoreML model loading hanging on the MLE5ProgramLibrary.lazyInitQueue after OS updates. A few things that helped me work around it: 1. Pre-compile to .mlmodelc instead of loading .mlpackage at runtime The AOT recompilation path (which is what's hanging) gets triggered when the on-device compiled cache is invalidated by the OS update. If you ship a pre-compiled .mlmodelc built with the matching Xcode/SDK version, it often skips recompilation entirely: // Compile once at build time or first launch let compiledURL = try MLModel.compileModel(at: mlpackageURL) // Then load from compiled let model = try MLModel(contentsOf: compiledURL, configuration: config) 2. Load on a background thread with a timeout Since the hang is on a serial dispatch queue and the C++ exception bypasses Swift error handling, wrapping the load in a Task with a timeout at least lets you fail gracefully instead of getting watchdog-killed: let loadTask = Task { try MLModel(contentsOf: modelURL, configu

Update: I've reverted to using Claude in the Terminal. The implementation in Xcode 26.4 is just so godawful buggy that it's unusable. (I've discovered that if you quit and restart Xcode, the chat history suddenly contains TONS of text that wasn't showing up previously!) Whatever the reason, Xcode 26.4 is just crippled. I haven't tested the new 26.5 beta because you can't ship apps from it yet.

Seems to be fixed in Xcode 26.5 beta 1 :)

Thanks for looking into this. Here is a complete summary of our setup and what we have confirmed so far. App configuration: macOS app distributed via Developer ID (PKG installer) — not the Mac App Store Host app runs as a menu bar agent (LSUIElement = YES in Info.plist) NSApplicationActivationPolicy = .accessory The app runs continuously as a login item — it is always alive Network Extension is a System Extension (NEAppProxyProvider), always running alongside the host app What we have implemented: MXMetricManager.shared().addSubscriber(self) is called in applicationDidFinishLaunching in the host app — as early as possible A separate MXMetricManagerSubscriber is registered inside the Network Extension process at tunnel start Both didReceiveMetricPayloads: and didReceiveDiagnosticPayloads: are implemented On startup we also drain pastPayloads and pastDiagnosticPayloads to catch anything queued while the process was not running The subscriber object is kept alive for the full lifetime of both processes What we h

It suddenly started happening to me on Tahoe 26.4 running Xcode 26.4 on an M2 MacBook Air.

Hi, App crashes on launch on iOS 26.3.1 after building with Xcode 26.4. dyld: Symbol not found: MetricKit.mxSignpost Works fine on iOS 26.4+. FB: FB22384135 Anyone else seeing this or any workaround? Thanks.

Just chiming in to say I also am running into this. As my only machine is a 14 M1 Pro I am now out of luck in running Xcode at all for my projects

I tested Xcode 26.5 beta 1 (build 17F5012f), released on 2026-03-30, and the issue remains unchanged: app-hosted unit tests still fail on the same physical iOS 16 device with Logic Testing Unavailable.