I found a better solution for interaction Live Activity. You can create a struct impletion LiveActivityIntent then add it to widget target and app target. Create two files, one add to widget target, other one add to app target, each extension your Intent and write one same function. Widget target function can empty, app target function is real code. In perform call your function in extensions file. Above steps make sure compile success and when interaction intent, System will execute your real code in App Process.

@fehners My solution works with LiveActivityIntent because it will perform in app process. one more thing, intent struct must be marked public, else in release mode(debug mode is well), system cannot find your intent.

@sebj Try set 「Enable Debug Dylib Support」 to NO

@Mr. Jefferson I solved the problem. because your Intent openAppWhenRun = true, so the intent must be included in both the main target and the widget target

@PhonJac your LaunchAppIntent must included in main target

@DTS Engineer Hi, I'm having an issue with HealthKit background delivery on watchOS 11.3.1, I'm using HKObserverQuery and I'm experiencing CSLHandleBackgroundHealthKitQueryAction watchdog transgression crash. I confirm that I have called HKObserverQueryCompletionHandler correctly and in time. Is there any special requirement for the code to call HKObserverQueryCompletionHandler? For example, does it have to be in the main thread?

@DTS Engineer I have created a Feedback FB17024450 report and included more details about the environment along with additional video recordings. Hope this helps.

I have the same problem, I am monitoring HRV data using HKOberserQuery + enableBackgroundDelivery with HKUpdateFrequency.hourly . in HKOberserQuery i only gets the latest one HRV sample. I make sure HKObserverQueryCompletionHandler is called correctly, but I see a lot of CSLHandleBackgroundHealthKitQueryAction crash log on the watch logs, and I'm seeing the same logs on other apps too!

@DTS Engineer hi, Ziqiao I have a similar issue FB17024450, but there has been no progress. Could you take a look at it as well?

It seems that this issue has been fixed in the new beta version. @haozes