IssueTracker

Component used: RemoteListenableWorker Version used: 2.8.0-alpha04 Devices/Android versions reproduced on: Pixel 5 emulator with SDK 31 and 32

When a remote work request is cancelled, it leaves a bound connection to the remote worker service. This is unlike completed work where the connection is unbound and the remote service worker is allowed to stop.

The attached project is a slightly modified version of the WorkManagerMultiprocessSample project. The procedure is to start Remote Worker 2 and then cancel all jobs before it completes. The work request is successfully cancelled, but the connection is still active per dumpsys activity services. I thought it would be reused when scheduling another request, but it appears to be leaked. Each time the request is cancelled another connection is left behind. adb shell dumpsys jobscheduler shows no active jobs. The attached services.txt shows the leaked connections from the activity after cancelling jobs twice.