IssueTracker

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.