Illegal start of expression for Transaction without argument [117527454]

Fixed

Bug

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Oct 10, 2018 06:43AM

Component used: androidx.room:room-runtime, androidx.room:room-compiler
Version used: 2.0.0
Devices/Android versions reproduced on: N / A

@Dao
interface Foo {
@Query("SELECT * FROM bar")
fun getAll(): List<Bar>

@Transaction
fun getTransactionAll(): List<Bar> {
return getAll()
}
}

It generates

Foo.DefaultImpls.getTransactionAll(this, )

which cause the error (illegal start of expression) because of the extra comma.

Comments

yb...@google.com <yb...@google.com> Oct 10, 2018 03:55PM

Reassigned to da...@google.com.

ap...@google.com <ap...@google.com> #2Oct 24, 2018 04:10PM

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

da...@google.com <da...@google.com> #3Oct 24, 2018 04:12PM

Marked as fixed.

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 ?

ta...@gmail.com <ta...@gmail.com> #4Nov 13, 2018 12:00AM

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)

[Deleted User] <[Deleted User]> #5Jan 2, 2019 01:55AM

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

[Deleted User] <[Deleted User]> #6Jan 2, 2019 02:10AM

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 117527454