The documentation for how to handle focus & triggering the GKAccessPoint seems to be outdated for tvOS: https://developer.apple.com/documentation/gamekit/adding_an_access_point_to_your_game For tvOS specifically, the documentation has examples that refer to GKAccessPoint.focusFeedback and GKAccessPoint.shared.triggerAccessPoint which don't exist. I can use shared.isFocused() instead of .focusFeedback(), and .trigger {} instead of .triggerAccessPoint {}, but then it seems I can either set the focus to the accessPoint or I can trigger it, but I can't do both. For example, the following code captures the focus via a button, and then redirects the focus to the GKAccessPoint. You can still press the tvOS remote to visually show the button pressing, but it never prints out anything or triggers the access point. If you remove the .focusable(true) {...} section at the end, then the button will trigger the accessPoint, but it won't show it as focused. I seem to be missing something! Any ideas? #if os(tvOS) // this is used to "capture" focus invisibly, so it can be handed off to Game Center's GKAccessPoint VStack(alignment: .leading, content: { Button("") { print("Button representing GKAccessPoint was pressed!") GKAccessPoint.shared.trigger { print("\nI WAS TRIGGERED!!! by a button\n") } } .focusable(true) { isFocused in if isFocused { print("focused!") GKAccessPoint.shared.isFocused = true } else { GKAccessPoint.shared.isFocused = false print("NOT focused!") } } .opacity(0.1) }) .focusSection() #endif

Hi. If I use Xcode 15 to build wwdc2022-10054 (The SwiftUI Cookbook for Navigation sample project), it crashes when, on an iPad, you: Choose "Three Column Navigation" in the app (so you need to run this on an iPad or iPad simulator) Select category Dessert Select recipe Tiramisu** Select category Pancake Select any pancake recipe **selecting anything from "Kanom Thong Ek" or beyond will cause the crash. It seems to be a problem with selecting an item (recipe) when the previous recipe you selected is at least one position further down than the length of the current category recipe list. It's like SwiftUI is trying to deselect a previous list item or something, but the list is now shorter so that item doesn't exist anymore. I'm not sure if it crashed when built with Xcode 14, but it certainly does with Xcode 15.

Using Safari on macOS 13.4.1, installing Xcode 15 beta 2 is problematic. First time it downloaded Xcode & iOS 17 and the small metadata file. When I extracted the .xip file and started Xcode for the first time, it prompted me to install iOS 17 beta, but it was downloading it again so I cancelled: I couldn't get it to 'see' the already-downloaded iOS 17 DMG file (although I did mount the DMG file at first, not sure if that makes a difference). I eventually gave up and let it try re-downloading iOS 17. Then, it downloads the entire thing successfully, starts working on it, and then dumps out this error message: Registering simulator runtime with CoreSimulator failed. Domain: DVTDownloadableErrorDomain Code: 29 User Info: { DVTErrorCreationDateKey = "2023-06-22 03:32:23 +0000"; } -- The service used to manage runtime disk images (simdiskimaged) crashed or is not responding Domain: com.apple.CoreSimulator.SimError Code: 410 -- System Information macOS Version 13.4.1 (Build 22F82) Xcode 15.0 (22181.22) (Build 15A5161b) Timestamp: 2023-06-21T22:32:23-05:00 No other beta SDK would install, either. Eventually I went into Xcode Settings and under the Locations tab I changed Command Line Tools to Xcode 15 beta, and under the Platforms tab I deleted the first Xcode 15 beta's iOS 17 & watchOS 17 Simulators. Then I was running out of disk space because the failed downloads don't get deleted (where are they?) until you reboot your Mac. So I rebooted my Mac and went through these steps again. I managed to get watchOS 10 and tvOS 17 to download, but not iOS 17 or visionOS 1.0. Thanks EDIT: Perhaps I should mention that the Platforms tab of Xcode 15 beta 2 shows the last non-beta Simulator versions of OSes that Xcode 14.x is using (tvOS 16.4, watchOS 9.4), but doesn't show iOS 16.4 (but maybe because it's built in to Xcode 14?). Is that a clue?