“xcode github”

Hello @sheikhbayazid This is a great start! While we are unable to share exactly how Apple achieved this in the Music app, you might still find the following helpful: [quote='820932021, sheikhbayazid, /thread/820932, /profile/sheikhbayazid'] Should this be a custom container instead of fullScreenCover? [/quote] You might be looking for a sheet. Users can swipe down to dismiss a sheet interactively by default. .fullScreenCover has no built-in-swipe-to-dismiss, you must provide an explicit mechanism, like a dismiss button. For more information on Sheets see https://developer.apple.com/design/human-interface-guidelines/sheets [quote='820932021, sheikhbayazid, /thread/820932, /profile/sheikhbayazid'] How would you support both new and older iOS versions? [/quote] Configure the Xcode project to support the intended lowest OS version, then use conditionals to handle differences between iOS versions with availability checks such as #available if #available(iOS 18.0, *) { // Content in iOS 18.0 and later } e

@Jaanus Thanks for providing this. Do you have a FB open? Would you be able to upload the sysdiagnose as you said you have a macOS 26.4 with Xcode 26.5 and running a 26.5 simulator? Thanks for this!! Albert Pascual
  Worldwide Developer Relations.

Regarding the OAuth issue, I believe I need to sign in again if I switch Xcode versions. For example, I signed in with Xcode 26.4 to use Claude agent, but when I switched to Xcode 26.5 and tried to use the agent again. Xcode will show the authentication failure message. Failed to authenticate. API Error: 401 {type:error,error:{type:authentication_error,message:OAuth token has expired. Please obtain a new token or refresh your existing token.},request_id:req_011hoAXioU8pMsLnmS3c}

The latest Xcode Beta does not work either. Hangs almost immediately.

I started testing with 26.5 beta 1 and now the outputs are more 'friendly', but the Claude authentication problem is still there. My guess is that when updating the Claude SDK something changed and Xcode didn't keep up, because with Xcode 26.3 on an older version of the SDK everything was fine.

I have the same issue now after Xcode 26.4 has been released and changed these entitlements. My apps have been rejected with the following: Entitlement com.apple.security.hardened-process.enhanced-security-version-string value must be boolean and true. Entitlement com.apple.security.hardened-process.platform-restrictions-string value must be boolean and true. 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.

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.