IssueTracker

since these are in public API (:/) we need to do this in 1.2

Opening diff shortly

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

commit d576cbdc911cba16638a44fd8223391a90a07ef7
Author: Mike Nakhimovich <digitalbuddha@users.noreply.github.com>
Date:   Tue Aug 11 09:30:34 2020

    [GH] Hide deprecated internal API.
   
    ## Proposed Changes
   
    * `RoomDatabase.java` has protected `mCallbacks` field which is leaking in the API docs, we should @Hide it.
   
    ## Testing
   
    Test: Ran unit tests locally
   
    ## Issues Fixed
   
    Fixes: 76109329
   
    This is an imported pull request from https://github.com/androidx/androidx/pull/61.
   
    Resolves #61
    Github-Pr-Head-Sha: 6440daa3a63752c7f9d5ba2a390248cd85bc634f
    GitOrigin-RevId: fe92d8466a59b44b218b6ca3cbd57dcda17992f7
   
    Change-Id: Id599cdf5b02b32bdae0166266fb7da967598fe92

A       room/runtime/api/current.ignore
M       room/runtime/api/current.txt
M       room/runtime/api/public_plus_experimental_current.txt
M       room/runtime/api/restricted_current.txt
M       room/runtime/src/main/java/androidx/room/RoomDatabase.java

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

I think i was confused by your previous comment. You are right, we only use work-firebase for API < 23.
JobScheduler is used for API >= 23.

This issue should have been resolved in `alpha03` and `alpha04` (we addressed different parts of the problem). If you can reproduce this on a device, then can you do:

1. adb shell dumpsys jobscheduler for your app.
2. Reboot your device.
3. After the reboot, can you re-run adb shell dumpsys jobscheduler ?

I want to check if you see any differences in the jobs created before and after the reboot.

Thanks for your patience.

Actually for step 2, the easier thing to do is to force stop your app. You don't need to fo a full reboot.

I don't have to to rummage through traces. Here's code snippet that sends app into a crash loop. https://pastebin.com/NcTAnwjZ

I tried to reproduce this on alpha04. However, I cannot reproduce your issue.

For reference, this is what my activity looks like:

class MainActivity : AppCompatActivity() {
  override fun onCreate(savedInstanceState: Bundle?) {
    super.onCreate(savedInstanceState)
    setContentView(R.layout.activity_main)
    findViewById<Button>(R.id.scheduler_limits_testcase1).setOnClickListener {
      for (i in 1..100) {
        val a1 = newWorkRequest("--- A1 ---")
        val b1 = newWorkRequest("--- B1 ---")
        val b2 = newWorkRequest("--- B2 ---")
        val c1 = newWorkRequest("--- C1 ---")
        WorkManager.getInstance()!!
            .beginWith(a1).then(b1).enqueue()
        WorkManager.getInstance()!!
            .beginWith(a1).then(b2).enqueue()
        WorkManager.getInstance()!!
            .beginWith(b1, b2).then(c1).enqueue()
      }

    }
  }

  companion object {
    private fun newWorkRequest(message: String): OneTimeWorkRequest {
      val data = mapOf(TestWorker.KEY_MESSAGE to message).toWorkData()
      return OneTimeWorkRequestBuilder<TestWorker>()
          .setInputData(data)
          .build()
    }
  }
}

This is what my Worker looks like:

class TestWorker : Worker() {
  companion object {
    private const val TAG = "TestWorker"
    private const val MESSAGE_DEFAULT = "Default"
    const val KEY_MESSAGE = "KEY_MESSAGE"
  }

  override fun doWork(): Result {
    val message = inputData.getString(KEY_MESSAGE, MESSAGE_DEFAULT)
    val random = Random()
    val time = 500L + random.nextInt(300)
    Log.d(TAG, "Before. $message")
    Thread.sleep(time)
    Log.d(TAG, "After. $message")
    return Result.SUCCESS
  }
}

Do you have another part of your codebase that is scheduling jobs with JobScheduler?

We have 1 job that schedules once on app start, that's it.

I created a sample app.

For some reason it rarely crashes on AVD Emulator(Api 27), but 100% crashes on Genymotion Api 26 and my Xiaomi Redmi 7.1.2

You can try both Activities.

Hi, I've tried numerous times and have been unable to get your example to exhibit this problem.  Could you please update to alpha05 and reproduce it?  If you can reliably reproduce this issue, could you please do so with verbose logging enabled in your Configuration object (introduced in alpha05) and send us a bugreport?

I will some time later when I have time

Alpha 05, VERBOSE log level. Running the MainActivity in previous app.

Hmm, there is a possibility based on your stacktrace that you are running into b/111801342; something about these particular devices/emulators is leading to the issue manifesting like this.  This is fixed in alpha06 (which will be released later today).  Please update later today to check.

alpha 06, same thing

↑ This is Genymotion not Xiaomi log

I tried to reproduce this on a Genymotion emulator as well (on alpha04 and alpha06) on API 26. I cannot seem to.
I am marking this as not reproducible.

You tried to reproduce it on my example above?

How can you not reproduce it when I linked you the code to do so?

Same issue for me, "java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs", on Android 8.0.0 (HTC U11).

Just for my understanding, should we be able to enqueue more than ~100 WorkRequest ?

Yes, you should.  We found some edge cases where it's possible to schedule more work than allowable by the system and we're working on a fix.  Thanks!

Fixed in https://android-review.googlesource.com/c/platform/frameworks/support/+/726647.

A fix should be available in alpha07.

I still got the 100 job crash once using alpha-07

Still getting this crash with alpha08 from users (LGE Android 7 and Samsung Android 8):

Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1691)
       at android.os.Parcel.readException(Parcel.java:1636)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(DT:126)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(DT:95)
       at androidx.work.impl.Schedulers.schedule(DT:99)
       at androidx.work.impl.WorkerWrapper$1.run(DT:263)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:761)

#27, do you mind providing some more info about this?  How are you enqueuing your jobs?  Do you have a customized WorkManager Configuration (if so, what is it?)?  Did you have previously scheduled jobs using alpha07 or earlier or did you enqueue these jobs in alpha08?

Finally, if you can turn on verbose logging through the Configuration options, please send us the logcat using that.

I am en-queuing a OneTimeWorkRequest and listening to it's status change. On status change, I enqueue the same work request (with same tag and other constraints). For some time it runs fine, and then it suddenly crashes complaining of the 100 job crash and also of "WorkerWrapper: Didn't find WorkSpec for id"

Here's the crash log

08-31 17:31:19.892 9930-9985/com.example.agupta15.tryouts E/AndroidRuntime: FATAL EXCEPTION: pool-2-thread-1
    Process: com.example.agupta15.tryouts, PID: 9930
    java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
        at android.os.Parcel.readException(Parcel.java:1692)
        at android.os.Parcel.readException(Parcel.java:1637)
        at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
        at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
        at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
        at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
        at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
        at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
        at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
        at java.lang.Thread.run(Thread.java:761)
08-31 17:31:19.893 9930-9930/com.example.agupta15.tryouts D/status worker: id f5c workstatus state = ENQUEUED
08-31 17:31:19.893 9930-9930/com.example.agupta15.tryouts D/WorkManagerUtils: Schedule for Worker Class: Class Job Id: 100100
08-31 17:31:20.016 9930-9993/com.example.agupta15.tryouts E/WorkerWrapper: Didn't find WorkSpec for id 7f9fdb71-1c34-41e0-b012-97be46ecba85
08-31 17:31:20.020 9930-10011/com.example.agupta15.tryouts E/WorkerWrapper: Didn't find WorkSpec for id 6fdcb2ea-1f3c-4238-b175-15c4c4d80ec6

Please ignore the D/ logs (they are my own for debugging)

@Aloy: Which version of WorkManager are you using? Can you reproduce this issue with alpha08 ?
Also are you changing the default WorkManager Configuration ? Can you please send us a code snippet ?

For me alpha07 solved the problem.

This just have happened to a user. We use a unique work to download assets, that can be more than 100. We usually don't have issue but this time the user got:
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:2013)
       at android.os.Parcel.readException(Parcel.java:1951)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)

Device Mi A1 with Android 8.1.0. WorkManager 1.0.0-alpha06

This is the code:
        val workers = assets.map { assetModel ->
            val data = Data.Builder()
                    .putString(ASSET_UUID, assetModel.uuid)
                    .putString(ASSET_URL, assetModel.url)
                    .putString(ASSET_VERSION, assetModel.version.toString())
                    .build()
            OneTimeWorkRequest.Builder(AssetDownloadWorker::class.java)
                    .setInputData(data)
                    .build()
        }

        val continuation = workManager?.beginUniqueWork(
                DOWNLOAD_WORK_NAME + mainUuid,
                ExistingWorkPolicy.KEEP,
                workers.toList())

#32: As noted earlier, this is fixed in newer versions of WorkManager.  Please update to the latest version.

Sorry, for the wrong report. Seems to work fine for me now.

We are using alpha08 and we are still getting this exception. We use the WorkManager to send events to our backend. So we can enque a lot of requests (more than 100) in a short period of time.

We don't know exactly how to reproduce this error but we see in crashlytics that two users are getting this issue lots of times. The date we have about this users and crashes:

User 1, 11 crashes: Android  7.1.1 Nubia NX591J
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1692)
       at android.os.Parcel.readException(Parcel.java:1637)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
       at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
       at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
       at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:761)

User 2, 17 crashes: Android 7.0 Asus X008D
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1691)
       at android.os.Parcel.readException(Parcel.java:1636)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
       at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
       at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
       at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:761)

Yeah.. a fix should be available in alpha09 shortly. The relevant issue is https://issuetracker.google.com/issues/115560696

This was happening on android.arch.work:work-runtime:1.0.0-alpha01

This is not still happening on version :1.0.0-alpha09

Hi, this still happening in 1.0.0-alpha09. Only devices with 7 and 8 versions of android are affected.

Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1967)
       at android.os.Parcel.readException(Parcel.java:1905)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:44)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:148)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:117)
       at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
       at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
       at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

The code, that i used:

class App : MultiDexApplication() {
 
  override fun onCreate() {
    super.onCreate()
    Job.schedule()
  }
}

class Job(ctx: Context, params: WorkerParameters) : Worker(ctx, params) {

  override fun doWork(): Worker.Result {
    Log.d("-------------------Job is done!--------------------")
    return  Result.SUCCESS
  }

  companion object {
    private const val TAG = "my_job"

    fun schedule() {
      val workManager = WorkManager.getInstance()
      val work = PeriodicWorkRequest.Builder(Job::class.java, 1, DAYS).addTag(TAG).build()
      workManager.enqueueUniquePeriodicWork(TAG, KEEP, work)
    }
  }
}

In our case, seems that alpha-10 is not having this crash anymore. After four days in production no events have happened.

Ok I'm updated to alpha10, and watching for statistics now.

Updated to alpha10 and the crash persisted. Doesn't seem to be fixed, so reverting my app back to firebase jobdispatcher.

We had this problem on aplha08, aplha09 and now on alpha11. On alpha11 it is happening less than before, but there are still many crashes.

I'm removing WorkManager from our project and getting back to JobScheduler.

I can't believe that Google is not able to fix a base/core issue in this library for 11 versions straight, it is totally unusable with this bug.

Is there a way we can raise this ticket to someone more competent that is able to solve this problem???

Such a shame Google...

We have fixed all known issues around this. If you are still seeing this, feel free to send us a stacktrace and a sample app that reproduces the problem.

Sorry, I could not reproduce the issue myself. I lost a whole day trying to reproduce the issue and I could not do it, but it does not mean that the crash is not happening.

On 50K users using the app (with alpha11 library), we see that around 0.1% (50) of them have these crashes. It only happens on Android version 7 and 8.

We had a bigger crash rate before upgrading to alpha11, but the bug is still happening.

The only traces I have are these from Fabric:

Android 7
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1701)
       at android.os.Parcel.readException(Parcel.java:1646)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
       at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
       at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
       at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:762)
           
           
Android 7  
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1691)
       at android.os.Parcel.readException(Parcel.java:1636)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
       at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
       at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
       at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
       at java.lang.Thread.run(Thread.java:761)
           
           
Android 8
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
       at android.os.Parcel.readException(Parcel.java:1975)
       at android.os.Parcel.readException(Parcel.java:1913)
       at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)
       at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:44)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
       at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
       at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
       at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
       at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
       at java.lang.Thread.run(Thread.java:764)

           
It is happening on a wide range of devices (some of them):

Samsung Galaxy S7 (herolte),
Samsung Galaxy S7 (heroltebmc), Android 7.0
Samsung Galaxy Note5 (noblelte), Android 7.0
Samsung Galaxy S6 (zeroflte), Android 7.0
Samsung Galaxy S7 edge (hero2lte), Android 8.0
Motorola Moto G (5th Gen) (cedric), Android 8.1
Motorola Moto G(4) Plus (athene_f), Android 7.0
LGE V20 (elsa), Android 8.0
LGE LG K20 (lv517n), Android 7.0
dream2qltesq, Android 7.0
Huawei 荣耀畅玩 6X (HWBLN-H), Android 7.0
Sony Xperia Z5 (SO-01H), Android 7.0
Sony Xperia XZ Premium (SO-04J), Android 8.0

I think what might be happening is that some of the already scheduled jobs, may be stuck in a certain state.
You might want to push an update on the next version of your app, where you can cancelAllWork(), and reschedule all the Workers you need.

I have tried with cancelAllWorkByTag using the tag we used to create the jobs in the newest staged release but it did not help. We are still seeing the same crashes. We have also updated the lib to the latest (beta01) version.

cancelAllWorkByTag() only cancels work with tag.To be sure, you could cancelAllWork() [https://developer.android.com/reference/androidx/work/WorkManager.html#cancelAllWork()]
That way you are guaranteed to start from a clean slate, and then you can reschedule your work. Also, are you using a custom configuration when instantiating WorkManager ?

Yes, but we used a static constant in NotificationWorker.class to initialize it and used the same constant to cancel the work, so all workers should be stopped.

Here is the code:

        WorkManager.getInstance().cancelAllWorkByTag(NotificationWorker.TAG);

        PeriodicWorkRequest.Builder notificationsWorkBuilder = new PeriodicWorkRequest.Builder(NotificationWorker.class, NOTIFICATIONS_PERIOD, TimeUnit.MILLISECONDS);
        notificationsWorkBuilder.addTag(NotificationWorker.TAG);
        PeriodicWorkRequest notificationWork = notificationsWorkBuilder.build();
        WorkManager.getInstance().enqueueUniquePeriodicWork(NotificationWorker.TAG, ExistingPeriodicWorkPolicy.REPLACE, notificationWork);

If that is the only worker, then you are good. If there are other workers with other tags involved then using cancelAllWork() is what I would recommend.
Just to ensure that you are starting from a clean slate I would also try and call https://developer.android.com/reference/android/app/job/JobScheduler#cancelAll(), and reschedule work.

Yes, this is the only worker.  In the latest build I've added the cancelAllWork() call just to be sure that all work is cancelled (even we don't have more workers), but since we had a lot of crashes, I wasn't allowed to "play" anymore with WorkManager and we replaced it with JobScheduler for API23+ devices.

Hello,

We recently launched an update that includes "androidx.work:work-runtime:2.0.1", and we used it to schedule all our tasks now, in a satisfactory way. I just want to inform, (as you can see in the images attached below), that this problem keeps happening sporadically.

Keep in mind that the number of users affected in our case is small, since the app has several million active users, but it also starts to be worrisome, since the number of errors generated by each user is high.

The errors mainly occur in Android 6 and 7, and sometimes in 8, but especially in Android 7.

I do not expose implementation details, since the documentation of this SDK has been thoroughly studied, and in case there was a bad implementation, the number of errors would be infinitely greater.

Greetings.

We are having the same issue as in #52, (lots of crashes from small number of users) on WorkManager 1.0.1

Can you please add your notes to this bug report going forward.

https://issuetracker.google.com/issues/134058261

This bug report talks about this crash in the 1.x alpha era. So I just want to disambiguate the problem.

Updated workmanager from 1.0.0-beta02 to 1.0.1, as you recommended before, this should fix an issue.
Total crash count is raised drasticly, here we have stats for 40000 devices with 1.0.1 workmanager version: This issue has 46707 crashes affecting 347 users

Hi, unfortunately you're dealing with ~6 month old versions at this point.  You should upgrade to the latest version (2.2) - we won't be diagnosing issues on older versions anymore.

Hi, we're facing this issue too, also with v1.0.1.

We're using WorkManager#enqueue(OneTimeWorkRequest), instead of WorkManager#beginUniqueWork(OneTimeWorkRequest).

Upgrading to v2.x as you suggest forces us to migrate to Android X too. On v2.x I didn't see anything related in the changelog to justify the migration to Android X.. how can I be sure that migrating both Android X and work-runtime v2.x is gonna fix our issues?

Currently it's happening only in Android 7 (API 24), mainly in Motorola phones (70% Moto C Plus: https://www.gsmarena.com/motorola_moto_c_plus-8646.php)..

Thank you, regards!

We made a lot of improvements in 2.X apart from the AndroidX migrations. This problem should go away when you switch to WorkManager 2.2.0. We recommend updating to the latest version asap.

This is a bug.

the same problem continues to appear in androidx.work:work-runtime:2.0.1

androidx.work:work-runtime-ktx 2.5.0

Fatal Exception: java.lang.IllegalStateException
JobScheduler 100 job limit exceeded. We count 0 WorkManager jobs in JobScheduler; we have 1 tracked jobs in our DB; our Configuration limit is 20.
androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal (SystemJobScheduler.java:204)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SystemJobScheduler.java:132)
androidx.work.impl.Schedulers.schedule (Schedulers.java:108)
androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable (ForceStopRunnable.java:176)
androidx.work.impl.utils.ForceStopRunnable.run (ForceStopRunnable.java:102)
androidx.work.impl.utils.SerialExecutor$Task.run (SerialExecutor.java:91)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)
Caused by java.lang.IllegalStateException
Apps may not schedule more than 100 distinct jobs
android.os.Parcel.createException (Parcel.java:1958)
android.os.Parcel.readException (Parcel.java:1918)
android.os.Parcel.readException (Parcel.java:1868)
android.app.job.IJobScheduler$Stub$Proxy.schedule (IJobScheduler.java:184)
android.app.JobSchedulerImpl.schedule (JobSchedulerImpl.java:44)
androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal (SystemJobScheduler.java:186)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SystemJobScheduler.java:132)
androidx.work.impl.Schedulers.schedule (Schedulers.java:108)
androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable (ForceStopRunnable.java:176)
androidx.work.impl.utils.ForceStopRunnable.run (ForceStopRunnable.java:102)
androidx.work.impl.utils.SerialExecutor$Task.run (SerialExecutor.java:91)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)