Fixed
Status Update
Comments
su...@google.com <su...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
ro...@gmail.com <ro...@gmail.com> #3
yea i'll take it.
su...@google.com <su...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Version used:1.0.0-alpha02
Devices/Android versions reproduced on: all
Hi,
maybe I'm missing something in the documentation.
My intention was to create a periodic work that should run once a day (each 24 hours). I did two mistakes: I forgot to give the job a tag, and I forgot to check if the job was already in the queue before enqueueing it.
As result of error n2, each time that a user opens the app, a new job is enqueued. Only one job should be fired a day per user, but in my backend logs I can see that this happens multiple times per user.
As result of the error n1, I can not cancel those jobs (because they do not have a tag). I suppose the only solution is to uninstall the app and install it again.
Maybe it would be a nice feature to have a method to cancel all scheduled works, with or without tags. Or a method to get all current works, without tags, an then cancel them by Id.
Or at least to make the tag for a job mandatory, to be able to cancel the task in the future.
Another question that I did not find answer for is: what happens to current scheduled works, if the tag name is changed? Are the new one enqueued, and the old ones remains alive or what?
Thank and apologizes about my English.