I have received an invitation to a development team in the Apple Developer Program. Having filled the form out and completing the image challenge successfully, tapping on continue simply results in the button graying itself out. The JavaScript console shows the following error when this happens: { code: -4 data: "Destination unavailable. 500" message: "Application error." } I have tried this process in Safari, Chromium, as well as on mobile data on my iPhone, and the result is the same each time. Other messages in the console: [Warning] 30 console messages are not shown. [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 1 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Error] Blocked a frame with origin "https://appleid.apple.com" from accessing a frame with origin "https://appstoreconnect.apple.com". Protocols, domains, and ports must match. [Log] will send 'receivePingRequest' for rpc: 'formRendered', number of retries left: 0 (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] pm-rpc response recieved at – "" (widget-a72347aab29cc0b7fb82.js, line 2) [Log] success - rpc: 'receivePingRequest' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] - will send rpc message for 'formRendered' (widget-a72347aab29cc0b7fb82.js, line 2) [Log] failure - rpc: 'formRendered', reason: reached maximum retries. (widget-a72347aab29cc0b7fb82.js, line 2)

According to the UtilityWindow documentation: • They receive FocusedValues from the focused main scene in an application, similar to commands in the main menu, which can be used to display information on the active content as the user focuses on different scenes. This makes me think that any UtilityWindow, even across Scenes, should always receive @FocusedValues from the currently focused window of any scene. However, the following code doesn't quite work: @Observable class Info: Identifiable { let id = UUID() } struct ExampleApp: App { var body: some Scene { WindowGroup { ContentView() // Inside, it uses .focusedSceneValue(info) } UtilityWindow("Test") { UtilityWindowContent() } } } struct UtilityWindowContent: View { @FocusedValue(Info.self) var info var body: some View { Text(info?.id ?? "<nil>") // This always shows "<nil>" } } Here's some annotated screenshots of what's happening in a project: Menu bar commands do work with the same setup: As a workaround, attempting to use @FocusedValue in the App struct works, but as a result, the value appears to instantiate multiple times in the background, and they re-instantiate with every focus change. The @FocusedValue variable gets the correct instance, but it's needlessly initializing others in the background. This is on macOS 26.0 Tahoe Beta 8 (25A5349a).