Context

Component used: work-runtime

Version used: 2.4.0 Alpha 3

Devices/Android versions reproduced on: Android 7

Description

When running a Worker with constraints that calls setForegroundAsync() on Android 7 (and potentially earlier) the foreground service is started but not stopped after the worker has completed execution.

On Android 8, 9, and 10, the foreground service is stopped as expected when the worker completes and the notification is removed.

The bug only occurs for workers that have constraints. If no constraints are set, the behavior on Android 7 is correct as well.

Sample project

Github project https://github.com/otbinary/workmanager-foreground-worker contains a small sample app.

A foreground worker with a constraint (setRequiresBatteryNotLow) that sleeps for five seconds can be started by a broadcast intent:

adb shell am broadcast -n com.github.otbinary.fgworker/.StartSleepingWorkerBroadcastReceiver

Observations

On Android 7, WorkerWrapper.resolve() is called only for a ConstraintTrackingWorker instance that is wrapped around the actual SleepingWorker instance. ConstraintTrackingWorker.isRunInForeground() is false. resolve() therefore does not call mForegroundProcessor.stopForeground().

On Android 8+, resolve() is called for the actual SleepingWorker instance whose isRunInForeground() returns true. resolve() calls mForegroundProcessor.stopForeground().