xcode github

Hi, it's still not visible. I'm running Xcode beta 6. My app is an iPad OS app and I'm using RealityView. I can only see the Capture GPU Workload button. There's no way for me to debug my scene using the RealityKit debugger. Is it only available for VisionOS?

Hello, Thank you for your reply. Here are the details we observed: • iOS 18.6.2 (current release): authenticateHandler is invoked consistently — both when the Game Center sign-in UI appears and when the user taps Cancel. • iOS 26.0 beta 1 (first available build): Regression begins here. The Game Center sign-in UI is shown automatically, but pressing Cancel does not invoke authenticateHandler. The app receives no callback. • All subsequent iOS 26 betas (beta 2, beta 3, and the latest beta): Same behavior as beta 1. The issue has been reproducible across every iOS 26 beta so far. • Xcode versions used for testing: • Xcode 16.0 beta 1 with iOS 26.0 beta 1 • Xcode 16.0 beta 2 with iOS 26.0 beta 2 • Xcode 16.0 beta [latest] with iOS 26.0 beta [latest] So the regression is present from the very first iOS 26 beta through the latest beta. To help with investigation, I will provide a minimal sample project that sets GKLocalPlayer.local.authenticateHandler in viewDidAppear and logs w

Clearly Xcode 27 was a typo. My question is whether this behaviour was default or not for new Apps, If Apple expects developers to turn it on then its unlikely that it will end up using the second approach for the main app and any libraries that are overwhelmingly UI-focused.

Hi @RamiroDiaz-Latch, You wrote: In most cases, our code snippet works as expected, and the result is .success. However, we are also encountering other results, such as .denied, .alreadyPresenting, and .cancelled or .notSupported, which cause the Wallet to appear for users. [...] As @EtienneVTS mentioned, the API is intended to be used while an approved app is in the foreground. However, this requirement is indeed documented below: Use this method only in apps that must stay in the foreground when operating near NFC or other RF readers. This method prevents the device from automatically displaying the Apple Pay passes when it detects a compatible reader. This suppression occurs only while the app is in the foreground. The system automatically reenables the Apple Pay interface when the app goes to the background. If the app resumes, the system automatically suppresses the Apple Pay interface again. requestAutomaticPassPresentationSuppression(responseHandler:‍) https://developer.apple.com/documentation

Do devs realise they need to call stop access after resolving a bookmark? It's long been documented, but the reality is that: Most apps only interact with files in a limited/controlled way. Particularly on iOS, app lifetimes tend to be short enough that it hides most mistakes. Explicit start/stop makes it more obvious what to do, and the ideal API would be something like withAccess { callback } that would automatically stop access when the callback returns, or this: This works okay if/when file access is highly constrained, but it doesn't really work as well if you're working with a document over a very long period of time. More to the point, the APIs involved here are part of a LONG chain of evolution that keeps being expanded/tweaked/repurposed. For example, bookmarks weren't created to preserve security access; they were created to replace the Alias manager (from macOS Classic/Carbon). Similarly, security scoping in URLs is partially tied to file reference URLs (vs. file paths), but THOSE were really creat

Hi @haishu0, Please direct your code-level questions for this issue to DCloud—the third-party service and/or library presenting this payment error in your app. This error is not managed or generated by Apple. Cheers, Paris X Pinkney |  WWDR | DTS Engineer