This really isn't much of a solution unfortunately. Lots of my users run Series 4 & 5 Apple Watch models which are very capable for their needs. It's really hard to explain to them when these system issues occur and there's no fix third party developers can apply or guide them to.

😞 Oh well, thanks for getting back to me. I'll test when I can on WatchOS 27 and get another feedback in... I just didn't want WatchOS 26 being forgotten too when I think about half my users will still be on it this fall.

I can provide you the sample code if you like. Comes up straight away on device after the first background refresh handler call.

Bump for update as of today, iOS 26.5? I'm still wondering if I can alternate my 26.X code path, this worked well on 18.X

If the user has a complication for your app on their watch face, could you use the wigetkit extension to do the HealthKit work for you? It would run more reliably but might not fit your needs.... (plus you have to ask them to have a complication, many apps do!)

Are you able to run the same test on the 26.2 latest beta for us? Thanks

For reference, the release notes mention this issue being specific to SwiftUI Maps. I'm having the same problems with Swift Charts. iOS 26 RC, am having to ship a workaround as you suggested. Thanks

I can't access that link 😞

Thank you, this is all really helpful and appreciated. Cheers

This works great for MacOS, thank you! On Standby my app name is still displayed with just no widgets offered and a big "Add Widget" button which does nothing, is this a bug I should report? Presumably also .disfavouredLocations{.iPhoneWidgetsOnMac} is not needed if you have the data protection key enabled? As for CarPlay though, will the new widget support in iOS 26 also honour the .disfavouredLocations{} or data protection key?

I can answer 4, 5 and 6 if that helps. 4- Watch because iPhone cannot access the Health store what so ever when locked. 5- No. 6- None can be read. A little more info here incase it helps: https://developer.apple.com/forums/thread/780673

Many related WidgetKit issues unfortunately that have not yet been fixed, see one here: https://developer.apple.com/forums/thread/732751

Thank you for the suggestions. Will file feedback for now. I think the MeshGradient route it too far from the Charts API I'm otherwise working with. The other suggestions would work but would create stepped data and not a smooth view. One for enhancement I think.

Thank you, good to know this is the problem and not my code! Hopefully it makes it's way to the Xcode beta release notes

I've had no updates in my bug report if that's what you're asking! ... and the issue still persists.