I've noticed this issue for several years now and never found any information or documentation on what's going on. Thank you very much for clarifying this. Any further information on what defines "older workout data", as in how old, specifically interested in heart rate. Tine to get on adopting HKQuantitySeriesSampleQuery!

iOS 15 so far seems to be the only fix

This response made me chuckle! But yes I second that this happens quite a bit for me. Never on my development device without a passcode set, often on the other. Hopefully this might get fixed one day 🤞

I presume there's no chance of this being back ported to WatchOS 9.... some of my users will never update for various reasons including having an iPhone X stuck on iOS 16

I too am seeing this on Xcode 14.3

Oh, and also on the WatchOS beta

Ahh... That was my post too! 😱 I migrated to a single target a year back so I don't think this is my issue unfortunately.

Perfect, Thank You! For those interested, I created this modifier to work across all my small and medium widgets on iOS: extension WidgetConfiguration { func widgetOnlyOnHomescreen() -> some WidgetConfiguration { if #available(iOSApplicationExtension 17.0, *) { return self.disfavoredLocations([.standBy, .iPhoneWidgetsOnMac, .lockScreen], for: [.systemSmall, .systemMedium]) } else { return self} } }

And now with iOS 17 & WatchOS 10 release....

@developer555 This is exactly what I send to my users with problems: Change the complications that are not working to different apps. Reboot your Apple Watch. Launch the <my_app> watch app. Go back to your watch face and move the complications back to the ones you want. They should now update (fingers crossed). This works about 80% of times, I'm not sure this will ever be fixed as Apple are all WidgetKit only which is silly because my WatchOS 8 & 9 users are still on ClockKit and having problems

I did try a DTS (3791480) and never got a response after an initial further debugging email.... replied several times too and was charged for the DTS

This is great news. I would just like to clarify one part of this. Specifically, your last statement, providing an update to my app for customers on WatchOS 9 will resolve the issue. Does this need to be built with a specific version of Xcode or the SDKs? Only because I've done an update within the past month and am still seeing the issue for WatchOS 9 users. Or is it part of one of the latest WatchOS 9.6.X updates? (Which if it is I can direct customers to it)

Did you get any further with this? I've had various issues implementing the privacySensitive behaviour. Cheers

Does this apply to "complications" on the watch face that use WidgetKit? This is all not clearly documented IMHO.

@edford @Gong Just another update from me. With Xcode 15.3 and submitting an app update for all users I'm still seeing hundreds or even thousands of the same crash for users on WatchOS 9.6.3 I really don't believe this issue has been fixed, is there anything else that can be done to get this looked at. I've updated the feedback