Fail fast in image capture is save location is invalid [167697553]

Fixed

Bug

Status Update

No update yet.

Description

hu...@google.com

created issue #1

Sep 3, 2020 06:55PM

When the user specifies a destination to store the result of an image capture (with the use of outputFileOptions), the ImageCapture use case should verify whether this destination is valid before triggering the image capture request to the camera. If the destination is not valid, the operation should fail fast and the user should be notified about it.

Comments

ap...@google.com <ap...@google.com> #2Sep 10, 2020 05:41PM

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

hu...@google.com <hu...@google.com> Sep 10, 2020 05:42PM

Marked as fixed.

ap...@google.com <ap...@google.com> #3Sep 11, 2020 04:17PM

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 ?

ap...@google.com <ap...@google.com> #4Sep 18, 2020 09:00PM

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)

ap...@google.com <ap...@google.com> #5Sep 18, 2020 09:07PM

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> #6Sep 18, 2020 09:08PM

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.

an...@google.com <an...@google.com> #7Sep 18, 2020 10:03PM

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

ap...@google.com <ap...@google.com> #8Sep 18, 2020 10:04PM

I don't have to to rummage through traces. Here's code snippet that sends app into a crash loop.

https://pastebin.com/NcTAnwjZ