Thanks Quinn! Switching to the asynchronous activate function is exactly what fixed it. For other readers, here's the commit with the fix: https://github.com/leptos-null/WatchOS-WebSocket/commit/57d5899965063962d9fdf73b379e562658fa0084 Comments from the commit copied here for convenience: in my testing on watchOS 26.6 (on both an Apple Watch Series 7 and Series 10 with the same results), the synchronous AVAudioSession.setActive() version of this method does not throw, however calling the synchronous version is not sufficient to enable use of WebSockets. Additional note: [quote='899752022, DTS Engineer, /thread/773362?answerId=899752022#899752022'] when I start my audio session, watchOS presents its Connect a Device UI. [/quote] In my testing, this UI only presents if you pass .longFormAudio to policy in the setCategory call, which was not required for WebSockets to become available to the process.

Hi Quinn! Thanks for this update. I've published my demo project to https://github.com/leptos-null/WatchOS-WebSocket which uses NWConnection. I'm still having the same issues. I've included logs in the repo and I've copied that section here: Logs macOS: Launching on arm64, Version 26.5.2 (Build 25F84) Connecting to wss://echo.websocket.org Preparing connection WebSocket opened Received 32 bytes (text) watchOS: Launching on Watch7,9, Version 26.6 (Build 23U67) Activating audio session to unlock low-level networking Audio session active; route outputs: ["Speaker"] Connecting to wss://echo.websocket.org nw_endpoint_flow_failed_with_error [C1 echo.websocket.org:443 waiting parent-flow (unsatisfied (Path was denied by NECP policy), interface: ipsec2, ipv4, ipv6, proxy)] already failing, returning Connection waiting: POSIXErrorCode(rawValue: 50): Network is down Preparing connection Connection waiting: POSIXErrorCode(rawValue: 50): Network is down