Any update on this? Still not having any luck in Beta 4 getting this to work. I've also not seen it mentioned as fixed or as a known issue in the release notes....

Ok interesting. My intent code is unique for WatchOS and iOS because I have different parameters for the widget depending on platform. This also means having unique timeline code, one timeline provider per intent. My intent which is only targeted to my Watch app widget extension looks like this: struct WatchTrendWidgetIntent: WidgetConfigurationIntent { static var title: LocalizedStringResource = "Trend Widget Configuration" static var description = IntentDescription("Configure trend Health type Watch Widgets.") static var isDiscoverable: Bool { return false} init() {} func perform() async throws -> some IntentResult { return .result() } @Parameter(title: "Chart Health Type", default: TrendHealthTypeOption.restHR) var healthType: TrendHealthTypeOption? @Parameter(title: "Show Day's Date", default: false) var showDaysDate: Bool } I still need to test this on WatchOS 26 beta 4 but on beta 3 it worked.... In the timeline I do this: func recommendations() -> [AppIntentRecommendation<WatchTrendWidgetIntent>] { // Only used in WatchOS if #available(watchOS 26, *) { return []} else ........ } So hopefully this helps. One of the reasons I asked about if you have existing widgets was because of this problem here: https://developer.apple.com/forums/thread/788784 Was just wondering if this issue applied to you if you had existing Watch complication/widget users?

How are you planning to correctly adjust for the "timing dynamics between days". Is there a recommended solution that accounts for users sleep patterns including those who work shifts? Don't forget to also de-duplicate the sleep data, third party apps can write additional sleep events potentially causing you to count more sleep that actually occurred!

May not be super helpful but for a reference point, I am not seeing this on WatchOS 26 beta 3. Although there's been the some glitches loading the intent configuration UI and it's also unreliable in the Apple Watch app Face Gallery, I just wanted to say this might be something in your setup. Maybe creating a new intent with a single BOOL parameter might be a good test, although that will also need a new IntentTimelineProvider. Are you planning on moving from StaticConfiguration to AppIntentConfiguration for your Apple Watch widget/complications?

This issue remains and still seems like a glaring omission or that I must be missing something. I'll open a DTS as a last resort and report back if I get any useful details on migration strategies. If anyone else if having this issue please Boost the post! Thanks 🙏

Following some further work I think the accepted and recommended answer is actually not all that clear. From some further testing I've found that the following code works just fine in my WidgetConfigurationIntent for conditionally hiding parameters based on the widget family.... Should the statement "" actually be "Parameters cannot be conditionally hidden based on variables passed into the intent"? Thanks static var parameterSummary: some ParameterSummary { When(widgetFamily: .equalTo, .accessoryRectangular) { Summary("Test Info") { \.$hideAverageMarks \.$extendChart \.$showDaysDate } } otherwise : { Summary("Test Info") { \.$recentValueFormat } } }

I would just say this seems like a flawed approach for a HealthKit based app. I don't know many Watch apps which users operate whilst their iPhone is unlocked. If their iPhone isn't unlocked, there will be no access available to their HealthKit HealthStore on that device. If you can ask users on the Watch app to also unlock their iPhone - great. Otherwise I'd stick with what you have available on the Watch.

Yes, fingers crossed we get some direction or clarity from Apple here because after all these feedbacks, it's like it isn't considered an issue. I've since found an example of where on Apple Watch they seem to have solved this. The "Weather Details" widget/complication which I used in WatchOS 11 wasn't removed from my Watch face after the WatchOS 26 update. In WatchOS 11 it offers no configuration, in WatchOS 26 it does (screenshots here). Unless Apple just made all their Apple Watch widgets/complications AppIntentConfiguration instead of StaticConfiguration from the beginning, they must have had another way to migrate this whilst is persisted on my Watch face. 🤞

Hi Ziqiao, Thank you very much for the reply and details on this issue. This information is helpful. If I could just specifically clarify a couple of points just so it's really clear. When the background HealthKit observer query does wake my Watch app in the background and I call WidgetCenter.shared.reloadAllTimelines() before the completion handler, does this remove one of my separate widget extension budget's 4 hourly reloads? With regards to BGAppRefreshTaskRequest, I am confused here. Xcode does offer some supported modes to use this with Watch apps and the link you provided does show availability from WatchOS 6.0+.... Sorry I'm probably missing something here! Many thanks

I have solved this problem. The answer was in the WWDC25 video Get to know App Intends. Here's an example of an WidgetConfigurationIntent to toggle a chart showing data points on or off including icons for the two data point display options. struct WatchDataPointsWidgetIntent: AppIntent, WidgetConfigurationIntent { static var title: LocalizedStringResource = "Data Points Widget Configuration" static var description = IntentDescription("Configure individual data point display for Watch Widgets.") static var isDiscoverable: Bool { return false} init() {} func perform() async throws -> some IntentResult { print("WatchDataPointsWidgetIntent perform") return .result() } @Parameter(title: "Chart Display Options", default: ChartDataPointsOption.showDataPoints) var showDataPoints: ChartDataPointsOption? static var parameterSummary: some ParameterSummary { Summary("Chart Options: \(\.$showDataPoints)") } } enum ChartDataPointsOption: String, AppEnum { case showDataPoints case hideDataPoints static let typeDisplayRepresentation = TypeDisplayRepresentation(name: "Chart Display Data Points") static let caseDisplayRepresentations: [Self: DisplayRepresentation] = [ ChartDataPointsOption.showDataPoints: DisplayRepresentation(title: "Individual Data Points", image: .init(systemName: "chart.dots.scatter")), ChartDataPointsOption.hideDataPoints: DisplayRepresentation(title: "Percentiles Only", image: .init(systemName: "chart.line.uptrend.xyaxis")) ] }

Is it possible that this isn't actually a TabView but instead a custom sheet that has the interactiveDismissDisabled(_:) and .presentationDetents() maybe? Just a thought anyway as the map behind is unchanged by selections on the bottom buttons.

I've filled a feedback for this after WWDC 23 and 24. Here's the latest one FB13879424 This is really important. Let's 🙏 for WWDC25

Just want to expand a bit on the answer here. Yes Widgets can access the Health store. However, you need other remember that the Health store is only available when the device is unlocked. I will list a few limitations that come to mind from this. There's currently no way to request widget timeline updates only when the device is unlocked. There's currently no way to get reliable updates for iPhone widgets mirrored on Mac that include Health data, these will only update when the user unlocks their iPhone. Widgets on the iPhone Lock Screen can only update their Health data when the device is unlocked, this means if you're displaying a step count for example, it won't update throughout the day automatically. The same also applies to widgets in the Standby mode on iPhone. I've previously posted multiple feedback regarding this. The latest one is FB13879739 although it was closed... maybe we'll see some improvements here one day.

I would say post some screenshot examples of this. I'm fairly sure it's not possible with the existing APIs and they get around it by having the same background photo that you use for your home screen.

Similar thread now started here: https://developer.apple.com/forums/thread/763164