IssueTracker

Thank you for the quick fix.
Is there an ETA for the next release?

2.2.0-rc01 should be out this week.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit a1957df3709a06f4e6482fb0e4d39ded4f230a70
Author: Rahul Ravikumar <rahulrav@google.com>
Date:   Mon Jul 29 09:48:05 2019

    Workaround NPE in PersistableBundle.getExtras().
   
    Test: Existing unit tests pass. Ran integration test app.
    Fixes: b/138441699
    Change-Id: I0b48e0009a7d83c343a3d26112b94c057470c281

M       work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobService.java

https://android-review.googlesource.com/1092870
https://goto.google.com/android-sha1/a1957df3709a06f4e6482fb0e4d39ded4f230a70

  The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/)
  Release Track: (https://android-build.googleplex.com/coastguard/dashboard/6206758647365632/#/cherrypickHistory/all)
  Created: 2019-07-29 19:41:55.445144+00:00
  Changes: aosp/1092870
 

1,751 crashes from 383 users in my beta channel.  

I have reverted back to the 2.4.0 version of the library and the crashes have stopped.

No, the Play console only contains the following crash information:

This is from a Samsung S20 running Android 10

java.lang.IllegalStateException:
  at android.app.ContextImpl.startServiceCommon (ContextImpl.java:1688)
  at android.app.ContextImpl.startService (ContextImpl.java:1633)
  at android.content.ContextWrapper.startService (ContextWrapper.java:683)
  at androidx.work.impl.Processor.stopForegroundService (Processor.java:312)
  at androidx.work.impl.Processor.stopForeground (Processor.java:222)
  at androidx.work.impl.WorkerWrapper.resolve (WorkerWrapper.java:446)
  at androidx.work.impl.WorkerWrapper.resetPeriodicAndResolve (WorkerWrapper.java:556)
  at androidx.work.impl.WorkerWrapper.handleResult (WorkerWrapper.java:461)
  at androidx.work.impl.WorkerWrapper.onWorkFinished (WorkerWrapper.java:341)
  at androidx.work.impl.WorkerWrapper$2.run (WorkerWrapper.java:318)
  at androidx.work.impl.utils.SerialExecutor$Task.run (SerialExecutor.java:91)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
  at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
  at java.lang.Thread.run (Thread.java:919)

Actually, I just found it in the local log on my test device:

10-27 05:17:18.804 E/AndroidRuntime(12498): java.lang.IllegalStateException: Not allowed to start service Intent { act=ACTION_STOP_FOREGROUND cmp=com.dvtonder.chronus/androidx.work.impl.foreground.SystemForegroundService }: app is in background uid UidRecord{507c6a5 u0a291 CRE  bg:+6h3m58s342ms idle change:cached procs:1 seq(0,0,0)}
10-27 05:17:18.804 E/AndroidRuntime(12498): at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1715)
10-27 05:17:18.804 E/AndroidRuntime(12498): at android.app.ContextImpl.startService(ContextImpl.java:1670)
10-27 05:17:18.804 E/AndroidRuntime(12498): at android.content.ContextWrapper.startService(ContextWrapper.java:720)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.Processor.stopForegroundService(SourceFile:312)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.Processor.stopForeground(SourceFile:222)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.WorkerWrapper.resolve(SourceFile:446)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.WorkerWrapper.tryCheckForInterruptionAndResolve(SourceFile:419)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.WorkerWrapper.interrupt(SourceFile:375)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.Processor.interrupt(SourceFile:331)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.Processor.stopWork(SourceFile:188)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.utils.StopWorkRunnable.run(SourceFile:73)
10-27 05:17:18.804 E/AndroidRuntime(12498): at androidx.work.impl.utils.SerialExecutor$Task.run(SourceFile:91)
10-27 05:17:18.804 E/AndroidRuntime(12498): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
10-27 05:17:18.804 E/AndroidRuntime(12498): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
10-27 05:17:18.804 E/AndroidRuntime(12498): at java.lang.Thread.run(Thread.java:923)
--------- beginning of main

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 2f84e04876c0454432cb5595c73b1b1c02156331
Author: Rahul Ravikumar <rahulrav@google.com>
Date:   Thu Nov 05 15:18:22 2020

    Stop foreground service and ignore exceptions.
   
    - There are bugs in the platform that causes an intent dispatch to fail.
      This happens because the service and the `uid` is still in the background even
      though this intent could have only been delivered _after_ startForeground(...).
   
    Fixes: b/170924044
    Test: Ran integration tests to  make sure existing functionality is not broken.
    Change-Id: I99dc8e3e334ccbf3a53aa475ae445560278c004a

M       work/workmanager/src/main/java/androidx/work/impl/Processor.java

https://android-review.googlesource.com/1489901

Silly question but when can one expect the next alpha or beta of Work to be released? I would like to get the fix for this issue deployed to my users.