Technically, if by being an alarm or similar, you were able to run in the background on watchOS, could you not use the CoreMotion framework to access the same data Apple uses to base it's sleep stages off? I think this would be a big uphill battle as the algorithms aren't public, you'd need to make your own. But just wanted to voice the option if it was possible?

And in WatchOS 27.0 release if anyone was wondering

It's not stopping me get a popup about 20% of the time I unlock my device asking me to review Health permissions for an app I already granted access. Bothering users, notifications etc... must be such a hard problem for Apple design to solve, I get it... But i really hope iOS 28 move toward disabling blocking notifications like these. They achieved is a couple of years back with the 20 & 10% battery alerts which now just show in the dynamic island area. I think maybe a non-auto-dismissing dynamic island for these permissions nags would work better. As for your point @mix717 yes this lets us query if we've then been limited in Health data scope.... but there's no way to easily deep link the user to the permissions field, and we can't just ask again. Instead they need to go hunting in iPhone Settings -> Privacy & Security -> Health -> App Name and once they get there the old one button "Enable all" is gone, it's a multi step process again 🤯

I would very much like this to still be solved, even better for WatchOS 10, 11 & 26 as well 😁

I don't believe there's an API for this. I'm pretty sure it came up in this years WatchOS lab at WWDC26 and no luck. It's been requested for a while but for what ever reason 🤷‍♂️

I've submitted a new bug report FB24132300 replacing FB22115840. The issue still occurs on the latest release of WatchOS 26.6 AND on WatchOS 27 beta 4. Have also provided an updated and simplified sample project in the feedback. Anyone? Thank you 🙏

I have the answer here I think. No, not only does the Watch have to be running WatchOS 27, it also needs to be paired to an iPhone with Apple Intelligence enabled. This is despite the fact that PCC queries from WatchOS 27 go straight to the server and don't require the paired iPhone at all 🤷‍♂️

Hi lliyanke! No, I put that feedback in Nov 18, 2025, it was like putting a message in a bottle and throwing it in the ocean.....😯 So yes, never heard anything which is odd given Snippets were new. I'm still seeing the issue in iOS 27, although I haven't rebuilt the app with the new SDK incase that could help...

I had this issue, I could only use Device Hub with my own devices, no simulator would appear and I couldn't "see" my app when running it on a simulator even though there was console output. The fix for me was rebooting my Mac so I presume it's a bug. Fingers crossed this works for you!

ECGs have dedicated sample data when using the simulator and the Apple Health app. Something similar for this and a few other key types like Heart Rate Notifications would be very useful.

The layout of the Search/Browse tab is much improved 👏

Sorry, I‘ve not been clear enough with the question, I’m trying to determine if the device is viewing the Health data via synchronised iCloud or directly on device. The reason being the data via iCloud is often is delayed and so I’m trying to ensure I can provide the right experience to the user and set expectations. My app displays Apple Watch Health data and generally the paired iPhone‘s Health data stays right up to date with Apple Watch, but this isn’t the case for the iPad that also accesses the same data via iCloud. It’s not explicitly clear, but this delay issue might be something that is improved with the new 27 releases?

Is there any documentation or guides anywhere to indicate the duration/type/intensity of workout required to generate these VO2Max and Cardio Recovery values?

@DTS Engineer Any updates on this given the recent updates with WatchOS 27? That being said, a lot of my users will be staying on WatchOS 26 so I'm really still looking for a fix there as well! 🤞

Any new updates on this @DTS Engineer ? I did add the details to the feedback but no update so far. Thank you