Status Update
No update yet.
Comments
ra...@google.com
I'm not sure how to edit the description. But forgot to add that this will work when the app is in the foreground. It just doesn't work when you lock your device. I test this by moving the app to the background and then locking my device and checking the logs in Android Studio.
va...@gmail.com
It would be great if you could prioritize a fix for this issue. Additionally, if there are any alternative ways we can address this from our side, please let us know. Thank you!
ra...@google.com
We also experienced issues with the new version 2.10.0. In our app a Job that is launched at start of the app is triggered and then immediatly cancelled because constraints are not meet anymore. I tried everything from putting it as a foreground job removing all constraints on the job but the behavior stay the same. I will rollback to 2.9.1 until it's fixed. You will find attached some logs of the WM in our app, take a look at job fec664f7-e40c-4df1-baca-3cbc7e1b1ff9.
va...@gmail.com
I've had for sure more than one occasion on my phone where the Work didn't get executed after I've left WorkManager.
Description
Component used: WorkManger Version used: 2.9.0 Devices/Android versions reproduced on: Google Pixel 6 Pro
I use WorkManager's
OneTimeWorkRequestto schedule Notifications that I want to display at a certain time. Plainly said, I pass the notification data that I want and calculate the initial day and pass it tosetInitialDelay. This works fabulously. The only problem seems to be when my phone is in battery saver mode and WorkManager does not get called. Sometimes, if I turn it off, the Work gets executed, but sometimes it is dropped.Is there any way I can tell WorkManager that the Work is important and should not be dropped / affected by the battery saver mode?