thanks _lipit, appreciate the context. I've seen bug reports linked in this format (FBXXXXXXX) in several screen time support threads but have never been able to view them myself (clicking them renders "feedback not found"). Just confirming that the workflow you're suggesting is filing a new bug report describing the behavior I see and linking your existing one? thanks

separately - do you have a good method of subscribing or being otherwise notified about developments in the screen time API? beyond manually checking https://developer.apple.com/forums/tags/screen-time do you have a good method of staying up to date on the latest and information and/or sharing on information with other developers that have production builds using the API?

Great suggestions thanks - neither worked unfortunately. I have an open TSI and an FB to try to get support on this - no response still. I'll update this thread when we figure out how to recover

I was told it was based on WebKit data from the past 30 days in this thread: https://developer.apple.com/forums/thread/725373

+1 @Engineer FB16428132 This is the single biggest problem our user base reports. For users with large browsing histories, the workaround of displaying an error behind the picker just adds more frustration, because they reload the picker, expand the relevant category (or search for their app) and it insta-crashes again.