Feature request: Custom Worker Exception Handler [261190695]

Fixed

Bug

Status Update

No update yet.

Description

ie...@gmail.com

created issue #1

Dec 3, 2022 07:17AM

Component used: WorkManager Version used: 2.7.1 Devices/Android versions reproduced on: all

When Worker throws an exception, current default behavior is to log this exception to Logcat. There is no way to customize this behavior.

...
catch (InterruptedException | ExecutionException exception) {
   Logger.get().error(TAG,
        workDescription + " failed because it threw an exception/error",
        exception);
} 
...

Some applications might want to have a different behavior. One example would be to use a custom logger, or upload an analytics event when such a case happens.

Today, Configuration class already provides a way to handle exception during initialization and during scheduling. This feature requests is to add a similar mechanism to handle exceptions from worker.

Comments

sa...@saket.me <sa...@saket.me> #2Oct 13, 2023 05:26PM

Yigit, do you have time to fix it?

reemission of the same liveData is racy

sa...@saket.me <sa...@saket.me> #3Oct 13, 2023 07:42PM

yea i'll take it.

se...@google.com <se...@google.com> Nov 28, 2023 03:09PM

Assigned to ku...@google.com.

ap...@google.com <ap...@google.com> #4Jan 23, 2024 04:12PM

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.

se...@google.com <se...@google.com> Mar 21, 2024 02:46PM

Marked as fixed.

na...@google.com <na...@google.com> #5Apr 17, 2024 05:17PM

just emitting same live data reproduces the issue.

@Test
fun raceTest() {
val subLiveData = MutableLiveData(1)
val subject = liveData(testScope.coroutineContext) {
emitSource(subLiveData)
emitSource(subLiveData) //crashes
}
subject.addObserver().apply {
testScope.advanceUntilIdle()
}
}

Issue 261190695