Hey @Ivan018 were you able to solve this issue? What solution did you go with?

Any idea on how Opal is able to achieve it?

Still haven't gotten any solution to this yet :(

Do you have any update on this? Facing the same issue here.

Having the same issue.Iit is less noticeable on a dev build but on a release, it is very common. No idea how to fix this issue. I wonder how apps like Opal do it so flawlessly

Any solution to have multiple schedules active? Not able to find an answer to this

@_lilpit is there a way to monitor multiple events/schedules concurrently? Running startMonitoring on the second event just overrides the previously created one, along with the appTokens selected for that event. So, creating a new event un-shields the previously selected app and starts monitoring the newly created one even if we give the event a unique name like : let event = DeviceActivityEvent( applications: activitySelectionData!.applicationTokens, categories: activitySelectionData!.categoryTokens, threshold: DateComponents(minute: limitDuration) ) let eventName = DeviceActivityEvent.Name(<uniqueId>) What is the best way to handle multiple events and schedules without having them interfere with each other? Also curious to know how to keep track of applicationToken for each event separately.

Yes, facing the same issue here when the version is updated, although the bug isn't consistent. We face it 50% of the times. When this happens, reinstalling the app/ granting the screentime permissions again solves this issue.

Facing the same issue here. For us, the whole process works as expected when we're in debug mode/ when the physical device is connected to Xcode. But when we try the same process after disconnecting the physical device from Xcode or if we try it on release mode, we don't get a callback to the app from the extension where we have the shielding logic in place. Trying to debug this from past 2 days, not able to find any solutions to it.