[Feature Request] Allow the injection of a Log interface. [117236003]

Feature Request

Status Update

No update yet.

Description

gr...@signal.org

created issue #1

Oct 4, 2018 04:05PM

I work on Signal, which has no metrics reporting, so we rely heavily on user-submitted logs when we have a problem. In order to keep a persistent log on the user's device, we've created our own Logger that encrypts logs and stores them on disk. However, because WorkManager logs directly to the default android Log, we can't capture those logs in our persistent logger.

It'd be great if we had the option to inject a Log interface in WorkManger.configure(), with the default one just being an Android logger.

Comments

ap...@google.com <ap...@google.com> #2Nov 30, 2018 09:46PM

Not at the moment. But we have been asked this before, so I will treat this as a feature request.

yi...@gmail.com <yi...@gmail.com> #3Jul 11, 2019 01:53PM

OK thanks. At the moment I am just adding the name to the Data for the work request and retrieving it in startWork(), which works well enough.

di...@gmail.com <di...@gmail.com> #4Feb 13, 2024 01:24PM

Bump -- if not a log interface, it would be useful to have some sort of callback to know why a job was stopped or to be able to get some diagnostics.

se...@google.com <se...@google.com> #5Feb 13, 2024 02:27PM

Bump -- if not a log interface, it would be useful to have some sort of callback to know why a job was stopped or to be able to get some diagnostics.

You should be able to use stopReason API for this (or use the similar api on ListenableWorker itself)

di...@gmail.com <di...@gmail.com> #6Feb 13, 2024 02:43PM

Thanks, I didn't know about that API.

Issue 117236003