[quote='885099022, kgaidis, /thread/821959?answerId=885099022#885099022, /profile/kgaidis'] [1] the ability to put "Apps With Screen Time Access" behind a Screen Time Passcode is a new thing since iOS 26.4 [2] This is just a typical engineering/product issue where introducing new features introduces more bugs. Keeping it simple == less bugs (now and in the future). [/quote] [1] Yes, that’s correct! [2 ] Unfortunately, this is also true…especially with the Screen Time APIs…the framework already has so many bugs and it seems like with every release new ones are added. Here’s just a small selection of undressed Screen Time API bugs: FB18764644 FB18061981 FB10393561 FB14237883 FB15190710 FB22279215 FB22256086 FB17902237 FB16121372 FB17777429 FB19200003 FB19118205 FB12456954 FB18633581 FB16409127 FB13593803 FB22562796

[quote='883980022, Quappi, /thread/821959?answerId=883980022#883980022, /profile/Quappi'] I cannot reproduce this on my device. [/quote] Hey @infovine and @kgaidis! Big sorry from my side for the misunderstanding, I can now indeed fully reproduce the issue unfortunately! If I go into the app-specific settings in iOS Settings, e.g. iOS Settings -> Apps -> one sec, I can simply turn off the Screen Time permission, rendering the recently introduced changes useless (no screen time code is required here). Thanks a lot for bringing this up! @DTS Engineer I have updated my radar accordingly, hope that helps to get this addressed asap: FB18804632

[quote='885415022, DTS Engineer, /thread/758325?answerId=885415022#885415022'] Looking at that it seems that the 26.5 betas should show improvements, but probably won’t fix all the cases of this. [/quote] Thanks for the update @DTS Engineer Quinn! What you’re reporting seems similar to my personal observations: with iOS 26.5 things might have gotten slightly better, but there are still some issues going on definitely. Have a great rest of the week!

[quote='852356022, DTS Engineer, /thread/758325?answerId=852356022#852356022'] found their way to the right engineering team [/quote] Hey @DTS Engineer Quinn! Do you have an update on this? We are seeing more activity on the iOS 26.5 betas regarding the screen time frameworks, so it might be that this particular issue is in the process of being addressed?

[quote='885406022, kgaidis, /thread/823431?answerId=885406022#885406022, /profile/kgaidis'] a lot of developers report instability around Screen Time API's and this can fix a lot of headache for both Apple and devs [/quote] Hey @kgaidis! Thanks a lot for sharing your experience with the screen time frameworks as well! Would you mind filing a feedback request about this particular issue as well and posting your feedback number afterwards? The component is: Developer Technologies & SDKs -> iOS -> Device Activity Framework. I believe feedback like ours helps the team to prioritize what to work on next.

[quote='885383022, kthchew, /thread/823420?answerId=885383022#885383022, /profile/kthchew'] You might also want to try reporting this at https://security.apple.com/reports, which has an option to report malware/phishing. [/quote] Hey @kthchew! Thanks a lot for your input – filing a security report was actually the first thing I did back in December. Unfortunately it was closed with this explanation: For reference, this was my report number: OE11004876244680 After that, I decided to file a feedback request instead. And since there hasn't been any response to that since December and I’m still receiving these invites regularly I decided to move to the forums here, hoping the right team sees it.

[quote='885208022, DTS Engineer, /thread/808470?answerId=885208022#885208022'] Provide a focused project showing what you trying to accomplish and that the API is doing currently. [/quote] Thanks @DTS Engineer Albert for your response. I believe it’s currently not required to add an additional sample project, as the Screen Time team has informed me that the issue is most likely resolved in iOS 26.5 beta. So far I wasn't able to reproduce the issue anymore. I was just confused by your comment above that mentioned updating all devices signed into a family account, since we also reproduced the issue on devices where the user’s own screen time was managed compared to an underage family member. The bug might apply to families managing their kids’ screen time as well, but we don’t have that use-case in our app. Anyway, I hope this all doesn't matter anyway since the bug is hopefully addressed!

[quote='885073022, DTS Engineer, /thread/808470?answerId=885073022#885073022'] that is about the age instead of the the family sharing features [/quote] Sorry, I’m confused @DTS Engineer Albert. This is neither about age range nor about family sharing features. This issue is (as described in my initial post) about DeviceActivityEvents firing their eventDidReachThreshold callback immediately instead of after the defined threshold. Hope that helps!

[quote='885186022, DTS Engineer, /thread/823431?answerId=885186022#885186022'] Please note that you can view the current status of your Feedback in Feedback Assistant under Resolution. [/quote] Thanks for your feedback @DTS Engineer! My feedback report Resolution status is unchanged: "Open". I just wanted to make sure it landed with the right team, because I haven't seen any updates so far.

[quote='872955022, DTS Engineer, /thread/812973?answerId=872955022#872955022'] As things currently stand, ExtensionKit on iOS [1] requires that the host and container apps be the same, that is, an app can only load extensions that are located within the app. [/quote] Hey @DTS Engineer Quinn! It would be great if that behavior could be re-evaluated (maybe in combination with a requestable entitlement) to allow inter-app compatibility. For example, we allow users to block apps in one sec during unfinished tasks in Structured. This is a very popular use-case, combining apps from two different third party developers to generate even more value. More info: https://one-sec.app/integrations/structured/ And it’s a bit unfortunate that we have to upload user data to a server instead of exchanging it directly on-device directly.

Apple has informed me that this has been addressed in the iOS 26.5 betas. So far, I am unable to reproduce on my device. But since this regression occurs rather occasionally, I am a bit careful to confirm the bug fix right away. Can anyone else still reproduce on iOS 26.5 beta? – Frederik

Hello Albert! Thanks a lot for getting back to me! [quote='884463022, DTS Engineer, /thread/808470?answerId=884463022#884463022'] Have you had the opportunity to test the latest iOS 26.5 beta 2 on the download site since yesterday on all your active devices that are signed into family accounts? [/quote] Indeed, we are quite positive that this has been resolved. It’s now been more than two weeks and I was not able to reproduce the issue in that time. I just wanted to take a moment to prevent any misunderstandings: This issue is not about family sharing features such as screen time management of an underage family member. Our app is targeted at individuals who want to manage their own Screen Time. Does this bug fix still apply? We’re using this permission to set up the app: import FamilyControls try await AuthorizationCenter.shared.requestAuthorization(for: .individual) – Frederik 🐻‍❄️ one sec app

[quote='876526022, Keatonmorehead, /thread/809823?answerId=876526022#876526022, /profile/Keatonmorehead'] Given that Apple Security confirmed this is expected behavio [/quote] This is most likely a misunderstanding and this is not expected behavior. They probably just denied the security bounty since this is not a security threat…if this was filed via Feedback Assistant the Screen Time team would probably fix that bug asap, so I wouldn‘t build any app UX on such a "workaround"

[quote='816561021, ShaunTraynor, /thread/816561, /profile/ShaunTraynor'] Render selected Screen Time metrics into a shareable image [/quote] This is technically not possible, since all screen time report rendering happens in a sandboxed process and is therefore not programmatically screenshottable. On top of that, this is against Apple’s Developer Program License Agreement which prohibits sharing Screen Time data: You and Your Application may not share device or usage data received through the Family Controls Framework or otherwise, beyond the family controls You provide, or the individual and their device, respectively. Source: https://developer.apple.com/support/terms/apple-developer-program-license-agreement/

[quote='820956021, hkbm215, /thread/820956, /profile/hkbm215'] If this looks like a platform bug, should I file Feedback Assistant? If so, what logs/artifacts are most useful? [/quote] I haven't directly seen this bug because my apps do not rely on the intervalDidEnd being called reliably – but I have seen similar things happening with didReachThreshold. Even if your observations ends up not being a bug, I would always file a report through the feedback assistant: -> They might improve the documentation based on your input to prevent any similar (hypothetical) misunderstandings from happening in the future. I’m not saying yours is a misunderstanding…there is of course the chance that this is a bug indeed – and the sooner you report it, the better. Make sure you file it against the correct components: Developer Technologies & SDKs -> Device Activity Framework Attachments: Sysdiagnose of the affected device. Screenshots / screen recordings. Or even better: a quick demo video. Bonus: Minimal reproducing Xcode project. Don’t forget to post your feedback number here on the forums so other developers can reference it in their radars as well to help get dupes matched quickly. Hope that helps!