+1 Similar thread here for .individual authorization: https://developer.apple.com/forums/thread/714651

+1 (thank you Thomas for being on top of this!) I had a user bug report of this happening where permissions are 'randomly' lost so DeviceActivityCenter scheduling starts returning errors as if there are no permissions. Radar here with some details (if more is needed, happy to help): FB12364989

Same: FB11836901 (has a testing app to reproduce)

+1 also submitted: FB13066529

OK this thread talks about the actual problem: https://developer.apple.com/forums/thread/745675

+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

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

Linked the feedback mentioned and here's mine FB11442734

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

Filed a similar bug here: FB14187336

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

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)

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.)

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).

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