We just run into the same issue, trying to run the intent from Spotlight results in Shortcuts error notification and when running the intent from interactive widgets, only part of the logic gets executed 🤯 I would have guessed prior experiencing this, that triggering App Intent would launch the app if it were quit before. Here is the error message from screenshot so others might perhaps find it: "The operation couldn't be completed. (WFBackgroundShortcutRunnerErrorDomain error 1.)"

Just opened feedback if anyone wants to reference it: FB13210566

I have also filled a feedback if anyone wants to reference it in their report: FB13092595

We are also noticing the same issues on iOS 17 now.

How do you know about that limit? Is it documented anywhere?

Will do, we have Feedbacks opened for various activity report issues but not this one yet.

Ended up with the ViewThatFits solution that tries to fit as many rows as possible.

Upon further investigations it seems these issues aren't iOS 16.6 exclusive. By digging through the Xcode Organizer (with the filter set to last year) I found similar ones for iOS 16.4 from April and later for iOS 16.5. But nothing prior to iOS 16.4. Since our app has been out on the day iOS 16 was released this is suspicious. Either the Organizer doesn't show the crashes or they weren't happening. Check the stats below:

Hello, with 16.4 there is now search - although it would be nice to be able to control the navigation title or be able to hide it.

+1! This is also huge issue with an app we are working on. We have restrictions in-app to prevent users from disabling shielding of apps (per their requests) but we cannot stop them going to Settings and just turning off the toggle for permissions which immediately disables all restrictions.

I solved this by restarting my Mac and it stopped asking

Creating new in-app purchase makes it available to include as part of new version submission. But the dialog does not offer to select in-app that was previously rejected. Seems like bug in ASC?

@Kmart did some days ago :-) FB11975397 Happy to add more details if needed

We managed to "fix it" by resetting the device to factory settings. Unfortunately this does not look like good solution to offer in support communications with our users.

This and other issues happen to us as well. Seems like Screen Time API problem.