Way too easy to lock yourself out

[cassidyjames]

While testing out the new Screen Time feature on my own account, I turned on the "Weekday" switch and then the session immediately crashed. My guess is that the default time was 5:33 when the end time entry was constructed, and then when I toggled it on, it was 5:34 so I was (attempted to be) logged out.

Luckily it seems something didn't save correctly, so I was able to log back in… but it seems like we should ensure a minimum time to be logged in and load the end time to some point in the future to help prevent that.

[4jNsY6fCVqZv]

In addition I would also like to share my observation:
After I flipped the switch, a few seconds later I received a triple warning #128 that I was about to be logged out. So far I had not yet set any time settings in the plugin. It probably just calculated the current system time as start and end point of my usage. It would be nice if at least the end point would be somewhere in the future by default, so that I don't have to react directly to prevent myself from being logged out.

[cassidyjames]

@4jNsY6fCVqZv thanks for filing that other issue as well. Yeah, it seems like setting the default to some point in the future (or not setting the end time?) could help resolve both of these—but the duplicated notification issue should also be investigated.