GBR007 - did you ever find a solution to this? We are experiencing the same issue on an app currently

Also seeing this - looks like a bug with Apple

Also following this. Same issue here

Same issue here.

Also having this issue. I found that it's related to encryption. The way we're able to reproduce is to delete app, fresh build. It'll work, but if we re-initialize the models a few times (for us models are initialized at launch so this means closing / opening the app 5-6 times), then it looks like Apple fails to decrypt the model. Presumably some sort of throttle on # encryptions per device. Deleting / reinstalling will refresh and you start again....

Same issue here. Following!

Same issue - following!

Also following this. I haven't seen any documentation on this yet..

Just to follow up on this, excluding .small means you will not customize the live activity on the smart stack on the watch, but it does still show up. We have a similar issue, where we have an iOS app with a watch companion. The challenge we have is during a workout (we're a workout app), we display a live activity on the phone, which syncs to the watch. The watch smart stack then shows TWO widgets: The native workout widget The mirrored live activity from the phone This feels a bit redundant and unnecessary, but from what I'm reading there is no way to disable mirroring of the live activity all together, only disable customization.

What about the case where a companion watchOS app is running a workout with WorkoutKit? We have a similar issue, where we have an iOS app with a watch companion. During a workout (we're a workout app), we display a live activity on the phone, which syncs to the watch. The watch smart stack then shows TWO widgets: The native workout widget The mirrored live activity from the phone This feels a bit redundant and unnecessary, but from what I'm reading there is no way to disable mirroring of the live activity all together, only disable customization.

Also having this issue

Did you ever find a solution to this? We are doing a very similar thing where we have a fullscreenCover that is using a custom binding... where the getter is bound to a piece of state that can change rapidly. We're seeing similar things in watchOS 11 and iOS 18 where sometimes the fullscreenCover will not dismiss.

We're having the exact same issue on watchOS 10 and 11, and with phones running iOS 17 or 18.