Answer: https://stackoverflow.com/questions/63291989/how-to-get-ecg-voltage-measurements-hkelectrocardiogram-voltagemeasurement-ios-1/63381214#63381214

I'm still experiencing this issue with the latest Beta 7. Any suggestions or still sit tight?

Thanks for the quick response! So previously I was unable to get the minimumScaleFactor to work. This is good. However, I still took your exact code and put it in a complication template. The text labels don't have spacing between them as with the stock complication. It won't let me post an image here or link to one, but either way, take the exact Gauge you had above, and wrap it in a preview and compare with the stock one shown in the preview, the text sizes and positions are significantly different. @available(watchOSApplicationExtension 7.0, *) struct GaugeSample_Previews: PreviewProvider {     static var previews: some View {         CLKComplicationTemplateGraphicCircularView(TestGauge())                 .previewContext() } } Also, completely separately, what's the purpose of the Image(systemName: "heart.fill") in your code, this has no effect for me?

Thanks, this alternative worked great. Although guess its still a bug as it shouldn't crash if it previously worked in WatchOS 6?

Ok, I do implement the  getLocalizableSampleTemplate(for:withHandler:) method. So should I not ship with any complication bundle at all. I assume there's documentation on this somewhere?

This has now been fixed

Any further suggestions here, still have no resolution for the issue. Thanks

Apple Documentation explicitly states: "if you want your placeholders to appear in the Face Gallery, you must provide a complication bundle that contains your placeholders." https://developer.apple.com/documentation/clockkit/creating_complications_for_your_watchos_app/adding_placeholders_for_your_complication Can we please get some further detail here?

Nope. I'm considering opening a TSI but really don't want to waste it if the response is just "This feature is not currently available, please file an enhancement request".

I'm also having this issue. I've submitted a Feedback on the issue and made a sample project which I attached. It's a basic project that just uses SwiftUI to implement a Tab View Application. Toggling the Full Keyboard Access on before launch causes this very basic app to grind an iPhone 12 mini to a halt on iOS 14.3

Edorphy, I'm not sure I can really comment on iOS 12.2, though I suspect Apple will only really investigate bugs with iOS 14 currently.... I've not bothered with a HKObserverQuery in the end as I wasn't able to get it to work reliably. Instead I just use the Widget update callbacks to do fresh HKSampleQueries. Regards Simon

Same here, so frustrating and so unnecessary to release software of this quality....

Did you get anywhere with this? I basically only want widget refreshes when the device is unlocked for the HealthKit data store. It seems frustrating to have to request updates every 15 minutes when most return no data because the device is locked. Ideally I'd like to say update every 5 minutes, but only when the device is unlocked, and preferable with a priority call on unlock. Along side this Apple Watch only syncs its HealthKit data to the watch periodically. Calling a widget refresh at this point would be perfect.

Yes of course, it's FB8970333. I filed it 6 months ago when I first thought it was a bug but heard nothing back so still wondering if its intended behaviour? The feedback include a dead simple sample project with similar to above code. Thanks

I've not been able to get the always on display feature working throughout the entire summer. My app has a deployment target of WatchOS 6 mostly to support Series 1 & 2 Apple Watch models. Do you think that I need to drop support for WatchOS 6 & 7 in order to get my app working with the Always On display for WatchOS 8? Because even in the latest RC build (RC Xcode 13, RC iOS 15 and RC WatchOS 8), I can't get it to behave differently from how it did with WatchOS 7 and the time. I've also tried adding WKSupportsAlwaysOnDisplay and setting it to TRUE. No luck.