Add RxJava 3 support to Room [152427884]

Fixed

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Mar 26, 2020 10:26AM

Room has support for RxJava 2 but since RxJava 3 is out, RxJava 2 is now in maintenance mode and it'll be supported until February 28, 2021. RxJava 3 is not as big update as RxJava 2 was so I think it may not be a lot of work to support it in Room.

From Room point of view I think the biggest difference is new package structure:

https://github.com/ReactiveX/RxJava/wiki/What's-different-in-3.0#package-structure

Not sure if it affects Room but RxJava 3 supports Java 8:

https://github.com/ReactiveX/RxJava/wiki/What's-different-in-3.0#java-8

RxJava 3 can live next to RxJava 2 in a project and there is an interop library that helps with making them work together:

https://github.com/ReactiveX/RxJava/wiki/What's-different-in-3.0#rxjava-2x
but I think that it would still be good to have direct RxJava 3 support in Room to make the adoption of RxJava 3 faster.

Comments

m4...@gmail.com <m4...@gmail.com> #2Mar 27, 2020 07:21PM

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

tz...@gmail.com <tz...@gmail.com> #3Apr 7, 2020 04:29PM

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 ?

qn...@gmail.com <qn...@gmail.com> #4May 25, 2020 08:58PM

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)

ai...@gmail.com <ai...@gmail.com> #5May 26, 2020 06:32AM

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

ap...@google.com <ap...@google.com> #6Jun 24, 2020 04:59PM

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.

da...@google.com <da...@google.com> Jun 24, 2020 05:00PM

Marked as fixed.

Issue 152427884