Code snippet in ListAdapterHelper reference doc. [70411933]

Verified

Bug

Status Update

No update yet.

Description

si...@google.com

created issue #1

Dec 9, 2017 03:35AM

https://developer.android.com/reference/android/support/v7/recyclerview/extensions/ListAdapterHelper.html

Code snippet shows UserAdapter constructor as follows:

public UserAdapter(ListAdapterHelper.Builder<User> builder) {
mHelper = new ListAdapterHelper(this, User.DIFF_CALLBACK);
}

As far as I can see, ListAdapterHelper.Builder does not exist. And the only usage shown for the UserAdapter constructor takes no parameters.

Comments

yb...@google.com <yb...@google.com> Dec 11, 2017 05:17PM

Reassigned to cc...@google.com.

cc...@google.com <cc...@google.com> #2Jan 8, 2018 09:35PM

Marked as fixed.

Bringing setMaxSchedulerLimit to say 49 doesn't help. Same error.

[Deleted User] <[Deleted User]> #3Jan 22, 2018 02:07PM

If you are using work-firebase then you should not be using JobScheduler directly. Can you please send us the full bug report so we can investigate ?

cc...@google.com <cc...@google.com> #4Jan 22, 2018 11:19PM

Status: Assigned (reopened)

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.scheduleInternal(Schedulers.java:104)
at androidx.work.impl.Schedulers.schedule(Schedulers.java:73)
at androidx.work.impl.WorkerWrapper.setSucceededAndNotify(WorkerWrapper.java:393)
at androidx.work.impl.WorkerWrapper.handleResult(WorkerWrapper.java:255)
at androidx.work.impl.WorkerWrapper.run(WorkerWrapper.java:181)
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)

cc...@google.com <cc...@google.com> #5Feb 23, 2018 06:35PM

Marked as fixed.

What do you mean I shouldn't use JobScheduler directly? Isn't work-firebase is just for <21 devices, otherwise JobScheduler always used?

cc...@google.com <cc...@google.com> #6Feb 27, 2018 09:23PM

Verified by cc...@google.com.

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.

Issue 70411933