Search results for

“Xcode”

93,853 results found

Post

Replies

Boosts

Views

Activity

Reply to NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
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
26m
NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
I'm implementing a NEDNSProxyProvider on macOS 15.x and macOS 26.x. The flow works correctly up to the last step — returning the DNS response to the client via writeDatagrams. Environment: macOS 15.x, 26.x Xcode 26.x NEDNSProxyProvider with NEAppProxyUDPFlow What I'm doing: override func handleNewFlow(_ flow: NEAppProxyFlow) -> Bool { guard let udpFlow = flow as? NEAppProxyUDPFlow else { return false } udpFlow.readDatagrams { datagrams, endpoints, error in // 1. Read DNS request from client // 2. Forward to upstream DNS server via TCP // 3. Receive response from upstream // 4. Try to return response to client: udpFlow.writeDatagrams([responseData], sentBy: [endpoints.first!]) { error in // Always fails: The datagram was too large // responseData is 50-200 bytes — well within UDP limits } } return true } Investigation: I added logging to check the type of endpoints.first : // On macOS 15.0 and 26.3.1: // type(of: endpoints.first) → NWAddressEndpoint // Not NWHostEndpoint as expected On both macOS 1
5
0
76
26m
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for co
3
0
59
44m
Reply to App Crash with mxSignpost function not found
[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
Topic: App & System Services SubTopic: General Tags:
1h
App Crash with mxSignpost function not found
Hi team: I recently update to Xcode 26.4, and I encountered crash when running to < iOS 26.4 both for physical device and Simulator with this log: dyld[1257]: Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF Referenced from: <164CCEB0-E1F8-3CE2-A934-2096C19C0A9A> /private/var/containers/Bundle/Application/EA709A68-F76F-4D97-85C6-B71D61D68389/xxx.app/xxx.debug.dylib Expected in: <9E5EC9BB-5828-329C-A2BC-038B67060298> /System/Library/Frameworks/MetricKit.framework/MetricKit Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF Referenced from: <164CCEB0-E1F8-3CE2-A934-2096C19C0A9A>x /private/var/containers/Bundle/Application/EA709A68-F76F-4D97-85C6-B71D61D68389/xxx.app/xxx.debug.dylib Expected in: <9E5EC9BB-5828-329C-A2BC-038B67060298> /System/Library/Frameworks/
4
0
112
1h
Xcode 26.4 is missing the documentation for Foundation
Upgraded to Tahoe 26.4 and Xcode 26.4 and realized Xcode is missing the documentation for Foundation. Occasionally, if other (not yet missing) documentation references a Foundation entity, such as a type, clicking on it may open in a web browser pointing to the externally hosted Apple documentation. Anyone else experiencing this or have a workaround (perhaps the documentation files are on disk but were somehow lost / disconnected from the Xcode doc browser)? I checked the release notes for 26.4 and for 26.3 but did not find a mention of anything like that. Filed an issue with Apple, please do too if you are affected so hopefully it will see some love and lead to restoring the documentation. Edited: found some possibly related files in my ~/Library and the newer version v302 (26.4 related, I think, is considerably smaller): du -sh ~/Library/Developer/Xcode/DocumentationCache/* | awk -F/ '{print $NF t $1}' v296 1.0G v302 507M
5
0
139
1h
Reply to IPhone fails to connect with Xcode in presence of multiple WebContentFilters
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
1h
IPhone fails to connect with Xcode in presence of multiple WebContentFilters
I am facing an intermittent problem where iPhones are failing to pair/connect with Xcode under Xcode -> Windows -> Devices and Simulators. This happens when more than one web content filters are present, for instance, I have my web content filter (FilterSockets true, FilterGrade Firewall) and there is also Sentinel One web content filter with same configuration. Note: We are not blocking any flow from remoted / remotepairingd / core device service / MDRemoteServiceSupport etc processes. But they do get paused and resumed at times for our internal traffic verification logic. So, we are trying to understand what impact our content filter may be having on this iPhone Pairing?? If we stop either one of the filters the problem goes away. I have tracked the network traffic to the phone, and it seems to be using a ethernet interface (en5/en10) over the USB-C cable. I can see endpoints like this: localEndpoint = fe80::7:afff:fea1:edb8%en5.54442 remoteEndpoint = fe80::7:afff:fea1:ed47%en5.49813
1
0
22
1h
CoreML MLE5ProgramLibrary AOT recompilation hangs/crashes on iOS 26.4 — C++ exception in espresso IR compiler bypasses Swift error handling
Area: CoreML / Machine Learning Describe the issue: On iOS 26.4, calling MLModel(contentsOf:configuration:) to load an .mlpackage model hangs indefinitely and eventually kills the app via watchdog. The same model loads and runs inference successfully in under 1 second on iOS 26.3.1. The hang occurs inside eort_eo_compiler_compile_from_ir_program (espresso) during on-device AOT recompilation triggered by MLE5ProgramLibraryOnDeviceAOTCompilationImpl createProgramLibraryHandleWithRespecialization:error:. A C++ exception (__cxa_throw) is thrown inside libBNNS.dylib during the exception unwind, which then hangs inside __cxxabiv1::dyn_cast_slow and __class_type_info::search_below_dst. Swift's try/catch does not catch this — the exception originates in C++ and the process hangs rather than terminating cleanly. Setting config.computeUnits = .cpuOnly does not resolve the issue. MLE5ProgramLibrary initialises as shared infrastructure regardless of compute units. Steps to reproduce: Create an app with an .mlpackage Core
1
0
146
4h
Reply to CoreML MLE5ProgramLibrary AOT recompilation hangs/crashes on iOS 26.4 — C++ exception in espresso IR compiler bypasses Swift error handling
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
Topic: Machine Learning & AI SubTopic: Core ML Tags:
4h
Xcode 26.4: Regressions in Intelligence features
Just installed the new Xcode 26.4 RC build (17E192) after happily using 26.3 for a few months. I'm noticing some immediate regressions in the Intelligence features: Frequent losing of OAuth token (Claude Agent). This had previously been fixed and now is back. Agent Thinking is constrained to thought bubble windows, which are (a) too small to read, (b) not scrollable when thinking goes beyond a few paragraphs. Yes they are tappable when thinking is finished, but this doesn't help. Due to (2), in deep thinking, it's impossible to follow progress beyond the visible window, so impossible to know if the agent is going off the rails. I'm noticing just more general slowness to complete tasks. Not just complete them -- it seems like it takes longer to START tasks, which is really weird. It sits there thinking for longer. Same project, same model as before. Every time you tap New Chat it presents both Claude and Codex choices, even if you're only signed into one. This turned a simple single tap into now a req
12
0
449
5h
Reply to Xcode 26.4: Regressions in Intelligence features
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.
5h
Reply to NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
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
Replies
Boosts
Views
Activity
26m
NEAppProxyUDPFlow.writeDatagrams fails with "The datagram was too large" on macOS 15.x, macOS 26.x
I'm implementing a NEDNSProxyProvider on macOS 15.x and macOS 26.x. The flow works correctly up to the last step — returning the DNS response to the client via writeDatagrams. Environment: macOS 15.x, 26.x Xcode 26.x NEDNSProxyProvider with NEAppProxyUDPFlow What I'm doing: override func handleNewFlow(_ flow: NEAppProxyFlow) -> Bool { guard let udpFlow = flow as? NEAppProxyUDPFlow else { return false } udpFlow.readDatagrams { datagrams, endpoints, error in // 1. Read DNS request from client // 2. Forward to upstream DNS server via TCP // 3. Receive response from upstream // 4. Try to return response to client: udpFlow.writeDatagrams([responseData], sentBy: [endpoints.first!]) { error in // Always fails: The datagram was too large // responseData is 50-200 bytes — well within UDP limits } } return true } Investigation: I added logging to check the type of endpoints.first : // On macOS 15.0 and 26.3.1: // type(of: endpoints.first) → NWAddressEndpoint // Not NWHostEndpoint as expected On both macOS 1
Replies
5
Boosts
0
Views
76
Activity
26m
Network Extension "Signature check failed" after archive with Developer ID — works in Xcode debug
I have a macOS VPN app with a Network Extension (packet tunnel provider) distributed outside the App Store via Developer ID. Everything works perfectly when running from Xcode. After archiving and exporting for Developer ID distribution, the extension launches but immediately gets killed by nesessionmanager. The error: Signature check failed: code failed to satisfy specified code requirement(s) followed by: started with PID 0 status changed to disconnected, last stop reason Plugin failed What makes this interesting: the extension process does launch. AMFI approves it, taskgated-helper validates the provisioning profile and says allowing entitlement(s) due to provisioning profile, the sandbox is applied, PacketTunnelProvider is created — but then Apple's Security framework internally fails the designated requirement check and nesessionmanager kills the session. Key log sequence: taskgated-helper: Checking profile: Developer ID - MacOS WireGuardExtension taskgated-helper: allowing entitlement(s) for co
Replies
3
Boosts
0
Views
59
Activity
44m
Reply to App Crash with mxSignpost function not found
[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
Topic: App & System Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
1h
App Crash with mxSignpost function not found
Hi team: I recently update to Xcode 26.4, and I encountered crash when running to < iOS 26.4 both for physical device and Simulator with this log: dyld[1257]: Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF Referenced from: <164CCEB0-E1F8-3CE2-A934-2096C19C0A9A> /private/var/containers/Bundle/Application/EA709A68-F76F-4D97-85C6-B71D61D68389/xxx.app/xxx.debug.dylib Expected in: <9E5EC9BB-5828-329C-A2BC-038B67060298> /System/Library/Frameworks/MetricKit.framework/MetricKit Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF Referenced from: <164CCEB0-E1F8-3CE2-A934-2096C19C0A9A>x /private/var/containers/Bundle/Application/EA709A68-F76F-4D97-85C6-B71D61D68389/xxx.app/xxx.debug.dylib Expected in: <9E5EC9BB-5828-329C-A2BC-038B67060298> /System/Library/Frameworks/
Replies
4
Boosts
0
Views
112
Activity
1h
Xcode 26.4 is missing the documentation for Foundation
Upgraded to Tahoe 26.4 and Xcode 26.4 and realized Xcode is missing the documentation for Foundation. Occasionally, if other (not yet missing) documentation references a Foundation entity, such as a type, clicking on it may open in a web browser pointing to the externally hosted Apple documentation. Anyone else experiencing this or have a workaround (perhaps the documentation files are on disk but were somehow lost / disconnected from the Xcode doc browser)? I checked the release notes for 26.4 and for 26.3 but did not find a mention of anything like that. Filed an issue with Apple, please do too if you are affected so hopefully it will see some love and lead to restoring the documentation. Edited: found some possibly related files in my ~/Library and the newer version v302 (26.4 related, I think, is considerably smaller): du -sh ~/Library/Developer/Xcode/DocumentationCache/* | awk -F/ '{print $NF t $1}' v296 1.0G v302 507M
Replies
5
Boosts
0
Views
139
Activity
1h
Reply to Xcode 26.4 is missing the documentation for Foundation
[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
Replies
Boosts
Views
Activity
1h
Reply to IPhone fails to connect with Xcode in presence of multiple WebContentFilters
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
Replies
Boosts
Views
Activity
1h
IPhone fails to connect with Xcode in presence of multiple WebContentFilters
I am facing an intermittent problem where iPhones are failing to pair/connect with Xcode under Xcode -> Windows -> Devices and Simulators. This happens when more than one web content filters are present, for instance, I have my web content filter (FilterSockets true, FilterGrade Firewall) and there is also Sentinel One web content filter with same configuration. Note: We are not blocking any flow from remoted / remotepairingd / core device service / MDRemoteServiceSupport etc processes. But they do get paused and resumed at times for our internal traffic verification logic. So, we are trying to understand what impact our content filter may be having on this iPhone Pairing?? If we stop either one of the filters the problem goes away. I have tracked the network traffic to the phone, and it seems to be using a ethernet interface (en5/en10) over the USB-C cable. I can see endpoints like this: localEndpoint = fe80::7:afff:fea1:edb8%en5.54442 remoteEndpoint = fe80::7:afff:fea1:ed47%en5.49813
Replies
1
Boosts
0
Views
22
Activity
1h
Clipboard issues with simulators
After updating to Xcode 26.4 the pasteboard sharing feature in the simulators doesn't work.
Replies
26
Boosts
0
Views
2.3k
Activity
4h
Reply to Clipboard issues with simulators
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.
Replies
Boosts
Views
Activity
4h
CoreML MLE5ProgramLibrary AOT recompilation hangs/crashes on iOS 26.4 — C++ exception in espresso IR compiler bypasses Swift error handling
Area: CoreML / Machine Learning Describe the issue: On iOS 26.4, calling MLModel(contentsOf:configuration:) to load an .mlpackage model hangs indefinitely and eventually kills the app via watchdog. The same model loads and runs inference successfully in under 1 second on iOS 26.3.1. The hang occurs inside eort_eo_compiler_compile_from_ir_program (espresso) during on-device AOT recompilation triggered by MLE5ProgramLibraryOnDeviceAOTCompilationImpl createProgramLibraryHandleWithRespecialization:error:. A C++ exception (__cxa_throw) is thrown inside libBNNS.dylib during the exception unwind, which then hangs inside __cxxabiv1::dyn_cast_slow and __class_type_info::search_below_dst. Swift's try/catch does not catch this — the exception originates in C++ and the process hangs rather than terminating cleanly. Setting config.computeUnits = .cpuOnly does not resolve the issue. MLE5ProgramLibrary initialises as shared infrastructure regardless of compute units. Steps to reproduce: Create an app with an .mlpackage Core
Replies
1
Boosts
0
Views
146
Activity
4h
Reply to CoreML MLE5ProgramLibrary AOT recompilation hangs/crashes on iOS 26.4 — C++ exception in espresso IR compiler bypasses Swift error handling
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
Topic: Machine Learning & AI SubTopic: Core ML Tags:
Replies
Boosts
Views
Activity
4h
Xcode 26.4: Regressions in Intelligence features
Just installed the new Xcode 26.4 RC build (17E192) after happily using 26.3 for a few months. I'm noticing some immediate regressions in the Intelligence features: Frequent losing of OAuth token (Claude Agent). This had previously been fixed and now is back. Agent Thinking is constrained to thought bubble windows, which are (a) too small to read, (b) not scrollable when thinking goes beyond a few paragraphs. Yes they are tappable when thinking is finished, but this doesn't help. Due to (2), in deep thinking, it's impossible to follow progress beyond the visible window, so impossible to know if the agent is going off the rails. I'm noticing just more general slowness to complete tasks. Not just complete them -- it seems like it takes longer to START tasks, which is really weird. It sits there thinking for longer. Same project, same model as before. Every time you tap New Chat it presents both Claude and Codex choices, even if you're only signed into one. This turned a simple single tap into now a req
Replies
12
Boosts
0
Views
449
Activity
5h
Reply to Xcode 26.4: Regressions in Intelligence features
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.
Replies
Boosts
Views
Activity
5h