Configuration.Builder public API is broken [352872245]

Fixed

Bug

Status Update

No update yet.

Description

dl...@lightricks.com

created issue #1

Jul 14, 2024 11:41AM

Component used: WorkManager
Version used: 2.9.0
Devices/Android versions reproduced on: N/A

WorkManager's Configuration.Builder exposes two functions which accept a `Consumer` arg (

https://developer.android.com/reference/androidx/work/Configuration.Builder#setInitializationExceptionHandler(androidx.core.util.Consumer) and

https://developer.android.com/reference/androidx/work/Configuration.Builder#setSchedulingExceptionHandler(androidx.core.util.Consumer)). The Consumer class is part of the androidx.core artifact, however, WorkManager does not expose the dependency to its clients, making the functions broken unless the client adds the dependencies manually.

Comments

da...@google.com <da...@google.com> Jul 16, 2024 01:35PM

Assigned to ku...@google.com.

ap...@google.com <ap...@google.com> #2Jul 16, 2024 04:06PM

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.

ku...@google.com <ku...@google.com> #3Jul 16, 2024 04:41PM

Marked as fixed.

We’re encountering a similar issue with our FileUploadWorker, which is constrained to run only when the network is available. After this version bump, we’ve noticed that our file uploads are failing due to DNS network errors, which have increased by 5x. This could be a result of the UploadWorker starting and resuming even when there’s no network connection. Looks like this recent commit may be related to the issue :

https://android.googlesource.com/platform/frameworks/support/+/8aa67b30ea5e50b3c0e89909990b5f53d159465d

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!

pr...@google.com <pr...@google.com> #4Sep 5, 2024 08:09PM

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.

Issue 352872245

Description

Issue summary

Comments

da...@google.com <da...@google.com> Jul 16, 2024 01:35PM

ap...@google.com <ap...@google.com> #2Jul 16, 2024 04:06PM

ku...@google.com <ku...@google.com> #3Jul 16, 2024 04:41PM

pr...@google.com <pr...@google.com> #4Sep 5, 2024 08:09PM

Add comment

Issue metadata