Same, I’ve filed a bug report as well, but no feedback software far… FB14082790 and FB14215618

That’s a good feedback, but I feel like this only explains 1% of the bug reports we’re seeing.

Thanks for the confirming the bug! We do file bug reports for every issue we see, but for the screen time API we rarely get any feedback there. Is there a better way to reach out? Writing feedback and "throwing it in a black hole" feels frustrating. There haven’t been any labs for screen time at WWDC this year, weren't able to get our questions answered. If this is a known issue, why should we still file a bug report? Could you maybe instead give us a prediction when this will be addressed?

Thanks a lot for the feedback on this! @Engineer it’s really hard for us to debug this from the outside and find workarounds, because we can’t actually see the code that decides when our callbacks are called. So it would be appreciated if the Apple engineers working on the screen time API could suggest a workaround and a timeline for when this will be addressed.

Thanks a lot for the update, I can confirm that its no longer an issue on iOS 18 beta 2. A bit of feedback: It would’ve been great to get a timely feedback on my initial question posted here. A workaround, or at least some kind of acknowledgement for the issue with an outlook when it will be addressed. My users have been stuck with a non-working browser extension for 3 months already, and we have no idea when iOS 17.6 will be released.

same here, any idea how to solve this?

Update: I have tried on iOS 17.5 but the problem is still occurring, so a workaround would be appreciated.

Thanks for acknowledging this, is there any known workaround until iOS 17.5 is released?