Users are still prevented from granting access to blood pressure on 26.5.1. This is a long time for users to be locked out of one of the more important metrics Apple Watch provides. How is this not a more significant priority?

Same issue. We saw this in the beta, but assumed it was too glaring to actually ship. It appears you simply can't get blood pressure on 26.5 at all without making the user go through a bunch of manual steps.

The watch does make outgoing network connections. For instance, I have a watch app that uploads CMMovementDisorderManager data to a server for use in a research/clinical environment. Currently the only way I know to stop trying uploads due to network connectivity is when those requests timeout. I don't understand why you keep saying that the only reason to want to know if watchOS has network connectivity is for audio streaming. I don't see that supported in the docs anywhere, NWPathMonitor simply doesn't work as documented. I don't understand why you keep responding as if developers are doing something weird to want to know if the device they are on has a network connection.

I don't see the connection between audio streaming and network reachability. NWPathMonitor is the documented apple API for doing this on watchOS (having no SCNetworkReachability to use there). What am I missing? I am also seeing this always return not satisfied. Does this need a radar? This is simply broken.