Fixed
Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
The issue does not repro on Android 9
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #3
mi...@gmail.com <mi...@gmail.com> #4
Thanks for the quick fix. Any ideas when the next release will be? If not I'll try and work around this issue by implementing some kind of rate limiter and replacing the bad worker if it fires too many times.
su...@google.com <su...@google.com> #5
I would expect the next release within the next ~2 weeks, but I can't guarantee that.
Description
Version used: 1.0.0-alpha10
Devices/Android versions reproduced on: Android 4.4 API 19 Emulator
The bug is pretty easy to reproduce:
1. Boot up a brand new emulator (Android 4.4 API 19), and set the time to current time minus one year
2. Now run an app that enqueues a unique periodic work using the api enqueueUniquePeriodicWork
3. Now change the time of the device back to present time
4. Notice the unique periodic work goes into an endless loop. The only way to fix this issue is to enqueue again, using ExistingPeriodicWorkPolicy.REPLACE