Hi there, thank you for the response. At the moment, I am not 100% clear on what's going on so don't want to go through the process of filing Feedback. My "updated" understanding is that the alarm maybe does go off, but there's some special behavior if the phone is not locked (ex. its in "foreground") or app is in foreground while the alarm goes off. If I lock my phone, even with 1 minute differential I see the alarm go off. If I don't lock my phone, what maybe happens (at least I sometimes see it in debugger) is that the app runs to receive the "alerting" update (even if its technically in background?), but there's no UI anywhere showing that the alert is going off. Sometimes I do hear the sound (there's sound of alarm going off with no UI anywhere). I utilized open source sample code around AlarmKit and for that I do see the UI appear, where maybe it does because they implemented the custom widget? (but even their UI still shows inconsistencies depending on state of device/app) Of course I could be confused (surely am somewhat!), but my wish is that it would just always show UI (Lock Screen or "notification") / play sound, no matter what state there is.

@Engineer Ok apologies for the delay and thank you for listening to the feedback! ❤️ The feedback is: FB17108036

actually maybe its not related to "SFSafariViewController" and rather any full-screen View Controller presented on top causes this bug

(but I do want to note that thank you for continued tries at fixing FamilyActivityPicker 🙏)

Yes started in 18.4 AFAIK (not reproducible on 18.3.2)

Also if the "FamilyActivityPicker" is in a "crashed state" this does not happen.

Another example in Beta 3 (latest as we speak): ~3h screen time and it says multiple BANKING apps have 2h+ screen time at the same time. Updated feedback where maybe this is related to picture-in-picture (that being said, I did not spend 2h in all these banking apps while in Picture in Picture - just pointing out why the bug could be manifested...maybe in picture-in-picture it starts calculating everything wrong).

the youtube website is blocked as well (which is a good and intended behavior IMO) IMO given the numerous documented problems where blocking one thing accidentally blocks another (ex. blocking m.facebook.com blocks Messenger app), my vote is that we get rid of these sort of policies all together as sticking to a clear rule (doing X blocks X) is better than being ambiguous I could be wrong, but it also sounds like the root of your problem is this ambiguity. Where if it didn't exist, this wouldn't be an issue? So, if I understand correctly, there's a root issue to fix that would automatically solve this too. A very classic human/programming problem where the second-order effects of a unstable principle (blocking X also blocks Y) "exponentially" (being a little dramatic 😅) explodes to introduce new problems (exponential because you try to patch the Y problem, where then the patch can cause Z problem, etc. etc.)

Different, but similar vibe to "iOS 18.1 Screen Time shows private system resources" (FB15476753) so I assume there is some work happening around the area of screen time tracking All of this also affects the Settings > Screen Time tab too (not just third-party API)

My app had instant, repeating (5+ per user), withCheckedThrowingContinuation crashes when building off Xcode 16 (non-beta) for iOS 18.0 users. Had to do an emergency release with Xcode 15 and that seems to resolve it. Issue in RevenueCat (popular SDK): https://github.com/RevenueCat/purchases-ios/issues/4177

Filed a similar bug here: FB14187336

+1 it’s a logical addition, should be relatively simple to do and something the users want!

Linked the feedback mentioned and here's mine FB11442734

Same: FB11988641 (will tag this post and FB11799302 too)

+1 Thank you for bringing this up! I posted (a much less clear explanation than this post) of encountering this issue: https://developer.apple.com/forums/thread/748542?page=1#782949022