Our freediving app for Apple Watch Ultra declares WKBackgroundModes "underwater-depth" and "workout-processing". During a session it runs an HKWorkoutSession, enables Water Lock and starts a WKExtendedRuntimeSession. While the diver is at the surface it sends small URLSession uploads: a live position share for the people watching from shore.
On an Apple Watch Ultra with its own cellular plan and the paired iPhone switched off, every URLSession request fails while the underwater-depth runtime session is running. We tested each piece on its own, checking connectivity every 10 seconds and logging URLSessionTaskTransactionMetrics.isCellular and NWPathMonitor.
Cellular only: with nothing running, 26 of 27 requests succeeded over cellular. Within seconds of the underwater-depth runtime session starting, requests time out (-1001) and NWPathMonitor reports no available interface. With the HKWorkoutSession and Water Lock running but the runtime session ended, 8 of 8 succeeded over cellular. Cellular returns within about 5 seconds of the runtime session ending.
Wi-Fi only (iPhone switched off, known Wi-Fi): 34 of 34 requests succeeded over the watch's own Wi-Fi in every stage, including while the underwater-depth runtime session was running.
Another shipping dive app loses cellular the same way when its dive session starts, so it does not appear to be specific to our app.
Steps to reproduce: on an Apple Watch Ultra with an active cellular plan, switch the paired iPhone off and move away from any known Wi-Fi network. In an app with the underwater-depth background mode, start a WKExtendedRuntimeSession, then make a URLSession request. It times out while the session runs, and succeeds again within seconds of the session ending.
Our questions:
Q1. Is cellular data intentionally unavailable to apps while an underwater-depth session runs, while Wi-Fi remains available?
Q2. Is there a supported way to send a small amount of data over cellular during an underwater-depth session (for example while the diver is at the surface) without ending the session?
Q3. If neither, we have filed FB25362581 asking for cellular to be allowed at the surface, as Wi-Fi already is.
We have a focused test project (about 140 lines) that reproduces it and can share it with DTS.
watchOS 27.0.1, Apple Watch Ultra 2, Xcode 27.1.
we have filed FB25362581 asking for cellular to be allowed at the surface
Thanks.
I think this is the best path forward for you here. I’m not sure if the current behaviour you’re seeing is intentional or not [1], but at some level that doesn’t matter. You want this to work, so if it’s intentional then this just becomes an enhancement request rather than a bug report.
As to workarounds, nothing immediately springs to mind. A watchOS apps doesn’t really have control over how system state affects network interfaces.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] Looking at the code I think it is, but this stuff is super complex so it’s hard to say anything definitively.