So i tried a different solution . It works 80% of the time but sometimes the value lags and idk why . I used deviceactivitymonitor extension to set thresholds every 30mins so when user's screentime reaches a certain value it fires.... so there's no saving or manipulating data . on the accountability partner's end they see 0.5hr+, 1.0hr+, 1.5hr+ etc . it updates only when the user crosses a registered threshold. Problem is sometimes it takes a while to fire ... it could lag for about an hour . eg if user screentime is 2hr43min it's still stuck on 1.5hr+ when it's supposed to be 2.5hrs+ . I don't know why this happens. Any ideas?
Topic:
App & System Services
SubTopic:
General
Tags: