Fixed
Status Update
No update yet.
Comments
mi...@gmail.com
ra...@google.com
ra...@google.com
> We accept pull requests! :)
Is there a public repo somewhere? I don't see any obvious repo for it inhttps://android.googlesource.com , and it doesn't seem to be inside https://android.googlesource.com/platform/frameworks/support .
Room supports final fields (yay!), which probably will suffice for many people with respect to this feature request.
Is there a public repo somewhere? I don't see any obvious repo for it in
Room supports final fields (yay!), which probably will suffice for many people with respect to this feature request.
mi...@gmail.com
Room supports immutability (it can use arg constructors) but does not directly support AutoValue. It is in the schedule but not high priority :/. Idk much about its internals at this stage so I'm not sure how we would implement it but should be totally doable.
Sorry we don't have the source release yet :/.
Sorry we don't have the source release yet :/.
su...@google.com
"It is in the schedule but not high priority" -- completely understandable.
"Sorry we don't have the source release yet :/." -- ah, OK, I thought perhaps with the pull request comment, that meant that there was a repo somewhere that I had overlooked.
Thanks!
"Sorry we don't have the source release yet :/." -- ah, OK, I thought perhaps with the pull request comment, that meant that there was a repo somewhere that I had overlooked.
Thanks!
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