Quagga not working anymore on Galaxy S10 / Android 10 / Chrome 86.0.4240.198

Quagga seems not to suddenly no longer work on the Galaxy S10, running latest Android 10 (QP1A.190711.020) and Chrome 86.0.4240.198 (seems like this could be the likely culprit).

Quaga.init completes successfully, the video stream is displayed, but no codes can be scanned. All I see in the log is an Invalid asm.js: unexpected token error message in the console, which I know from other projects is mostly harmless.

I tried with the latest 1.2.6 release, and tried also downgrading to 1.2.5, neither of which helped.

Any advice on how to debug this?

[ericblade]

In my app, I currently just use a drop-down selector that I have the user tell me which one works. I suspect that intelligently selecting would be down to providing some constraints to the quagga config object (and i have a note here somewhere that we need to be able to pass constraints to the enumerateVideoDevices function if possible)… if you can figure out what the aspect ratio is for the wide-angle that we don’t want to select, we could try to eliminate that range from the aspect { min, max } parameters in constraints. I’d like to know the answer to that one too 😄 so we could provide that as a sane default, and it would catch more error cases.

and thank you so much for the contribution. You might have no idea how much that is appreciated right now.

[ericblade]

This leads me to think of one of my first experiences with my LG G6 – on my G6 there are multiple cameras, one of which is a wide-angle lens, which doesn’t work at all to try to locate barcodes with, because everything is fish-eyed.

Before just resetting everything, I would check to see if there are any other logical camera devices with Quagga.CameraAccess.enumerateVideoDevices and try those out to see if your results are any better?