I posted a bug report - this is the number: FB20169923 Thanks for looking into this!

@Engineer This is not a crash but a UX issue, which I'd consider a bug for most if not all Shielding use cases. From my perspective the point of Shielding an app is to not distract or disclose anything from that app to the user. This works as expected for notifications, Live Activities in the Activity Centre, Widgets and the UI itself - with this one exception. I'd expect Live Activities to be shielded just like all other UI elements and notifications of the app. In our use case it provides a very high risk exposing the result which we're trying to protect the user from. Currently we've added a warning text that suggests the user should disable live activities for apps that risks spoiling the result, but obviously that's not the optimal behaviour.

I'm having a similar issue. My implementation works on iPadOS but so far I can't get it to work on MacOS Catalyst. Trying to figure out if I'm missing some configuration (already enabled UIApplicationSupportsIndirectInputEvents). Did you manage to figure it out?