Came across a case where the user was changing their clock on their device into an inaccurate time into the future.
They then enabled "offer tracking" in the extension, which caused Chrome to queue up the next scheduled run of the alarm at this future UNIX timestamp (NOW() + 1 minute).
They then proceeded to correct their device time back to the correct time, which caused the next run to be scheduled for 1d+ in the future.
To help prevent this, the service worker can look at currently registered alarms and their next schedule time -- and if it's too far into the future, reschedule them.
Came across a case where the user was changing their clock on their device into an inaccurate time into the future.
They then enabled "offer tracking" in the extension, which caused Chrome to queue up the next scheduled run of the alarm at this future UNIX timestamp (NOW() + 1 minute).
They then proceeded to correct their device time back to the correct time, which caused the next run to be scheduled for 1d+ in the future.
To help prevent this, the service worker can look at currently registered alarms and their next schedule time -- and if it's too far into the future, reschedule them.