Status Update
Comments
ra...@google.com <ra...@google.com>
ra...@google.com <ra...@google.com> #2
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.
ra...@google.com <ra...@google.com>
ap...@google.com <ap...@google.com> #3
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 <ra...@google.com>
ap...@google.com <ap...@google.com> #4
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.
Description
Component used: WorkManager
Version used: 2.10.0
Devices/Android versions reproduced on: Android 8.1, Android 9.
The issue is not reproduced on Android 15.
After updating the WorkManager library to v2.10.0 from 2.9.1 we noticed a reproducible crash related to running a worker in a separate process:
We have a worker that uses a service from the separate process. Work data builder:
Work request builder:
The issue is not reproduced if the work is not expedited.