Still seeing the issue with build from the latest Xcode 15 Beta 8 and devices running WatchOS 9.6.X😕

I've also found TSI's have slowed as we've approached the iOS 17 release. I. still have one waiting (3791480)

And so many more from me: Translated Report (Full Report Below) Hardware Model: Watch6,18 Identifier: Sim.HeartRate.watchkitapp.WatchWidgetKitExtension AppVariant: 1:Watch6,18:9 Code Type: ARM64_32 (Native) Role: Unspecified Parent Process: launchd [1] Date/Time: 2023-09-24 20:11:54.9181 -0500 Launch Time: 2023-09-24 20:11:54.0000 -0500 OS Version: Watch OS 9.6.3 (20U502) Release Type: User Baseband Version: 5.04.01 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: DYLD 4 Symbol missing Symbol not found: _$s7SwiftUI17EnvironmentValuesV9WidgetKitE05ShowsE13BackgroundKeyVAA0cI0ADMc Referenced from: <7BA88B36-F66D-3527-9C49-CE859AB79FCB> /Volumes/VOLUME/*/<APP_NAME>.app/PlugIns/<APP_NAME> Watch WidgetKit Extension.appex/<APP_NAME> Watch WidgetKit Extension **(built for watchOS 10.0 which is newer than running OS)** Expected in: <15E32CD8-4D76-3F93-9881-7F8FDBB8A288> /System/Library/Frameworks/WidgetKit.framework/WidgetKit (terminated at launch; ignore backtrace) Triggered by Thread: 0 Thread 0 Crashed: 0 dyld 0x6dba6c5c 0x6db48000 + 388188 1 dyld 0x6dbb231c 0x6db48000 + 434972 2 dyld 0x6dbb234c 0x6db48000 + 435020 3 dyld 0x6db4c740 0x6db48000 + 18240 4 dyld 0x6db4abe0 0x6db48000 + 11232 5 dyld 0x6db4976c 0x6db48000 + 5996

Feedback filed 1st August: FB12818485

I wish this was possible but fairly sure it's not. Also their relative dates that are available don't update in the WidgetLabel areas... Frustrating, yet another regression from WidgetKit

Still happening for devices running WatchOS 9.6.2 & 9.6.3 Any update on this Apple?

See new APIs in iOS 17 for a better solution to all this.

I too am seeing this issue where in the Console app (fine in Xcode) it won't show Logger debug message. Info ones are fine, OSLog works fine.... Running Xcode 15, MacOS 13.6, iOS 17.0.3 and WatchOS 10.0.2, its Apple Watch I'm trying to debug.

Could this be related to this post? https://developer.apple.com/forums/thread/741113

Is there a solution here to detect if Widget is displayed on Mac via iPhone? I want to have a button in my interactive widget to update Health data but this is no good on the Mac because generally the user's device will be locked and therefore the HealthStore will be unavailable.

This seems to be the case with all charts for .chartXSelection and .chartYSelection. Not sure what can be done.... the system .onTapGesture doesn't have this issue so depending on if you need to track the tap location, this might be a solution

@edford  Just an update to provide some new context with the recent WatchOS 10.3 release etc... I've done several updates to my app in the past few weeks and I still have issues from users running WatchOS 10.2/10.3 and WatchOS 9.6 For the WatchOS 9.6.3 users, I'm still seeing the exact same crashes as the one I submitted from September 23. For the WatchOS 10 users, I only see crash reports for users on 10.0, however I still get problems reported from users mostly around complications disappearing from their watch face. This is even from users running WatchOS 10.2, too early to say for 10.3 Should I reopen a bug report / feedback on this or is there something I'm still missing to avoid all this?

In the event that anyone at Apple ever reads these post and the filed Feedbacks...... This is still an issue on WatchOS 10.3

You can do something like this: AxisMarks(position: .leading, values: Array(stride(from: yMin(), through: yMax(), by: 5))){ axis in AxisTick(stroke: .init(lineWidth: 2.5)).foregroundStyle(.pink) AxisGridLine() AxisValueLabel("\(Int((Double(axis.index)*5) + yMin()))", centered: false) } AxisMarks(position: .trailing, values: Array(stride(from: yMin(), through: yMin()+30, by: 5))){ axis in AxisTick(stroke: .init(lineWidth: 2.5)).foregroundStyle(.indigo) AxisGridLine() AxisValueLabel("\(Int(5*Double(axis.index))+10)", centered: false) } } But then you'll need to normalise the values for the second axis hence all the hack code in my AxisValueLabel content. I don't believe there's a more straight forward solution to your problem currently.

I think you'll now need to implement the TimelineProvider calls but you can just return a SimpleTimelineProvider entry and ignore the content when creating the SwiftUI view for your app icon. Have a look at the Apple sample code from the WWDC22 talk Complications and widgets: Reloaded