Cristiano Coelho

Won't this make the camera start/stop process much slower, or does it only impact `startPreview` / `stopPreview` calls, which are not normally used unless `pauseAfterCapture` is used? Rather than that,...

> > Won't this make the camera start/stop process much slower, or does it only impact `startPreview` / `stopPreview` calls, which are not normally used unless `pauseAfterCapture` is used? Rather...

Can you test on Android 12 physical device? I'm not aware of any breaking changes in Android 12, but this interests me. The error itself is self-explanatory, the capture process...

I plan on start testing Android 12 around next week on a physical device, but until then I cannot test neither. Would it be possible for you to debug the...

@mortend just tested this on an Android 12 (Pixel 5) device and taking pictures worked just fine. Note that I am not using camera2 API, and I'm using the `cameraId`...

I think the default settings use camera1 so that should not be the problem. If it works setting the cameraId but it doesn’t when just using the default type (back...

Isn't `cameraId` a string? Although it is an int with Camera1, I believe it is a string with Camera2 (and on iOS), so you may want to handle that case.

Does this mean that `onStatusChange` might fire more than once after mount? Should there be checks to only fire it if the status did in fact change (e.g., compare prev/next...

Nice catch, looks good to me! Can you make sure your branch is up-to-date with master? Do you know any specific scenario where `sessionWasInterrupted` is not called and this is...

Do you know what devices this happens with? I've never seen this reported so far, but since I'm using `skipProcessing: true` and `fixOrientation: false` I wouldn't know if I have...