Eric Blade
well, bare minimum, it needs a callback passed to Quagga.onDetected() which will accept whatever the output from the scanning is, and some mucking around with the HTML to allow for...
@mtowniowa just updated with that.. sorry it's taken me.. :checks notes: a long time. i honestly thought codepen was collaborative, and that other people could edit my entry. OOPS.
could you post the output of navigator.mediaDevices.enumerateDevices().then(x => console.log(x)) on the device in question? perhaps followed by Quagga.CameraAccess.enumerateVideoDevices().then(x => console.log(x)) so we can see what it's getting, and what's happening...
Aha! Permissions issues. Chrome on Android also has permissions issues -- you can't see the list of cameras until after you've granted permissions to the site, but you can't get...
yes, my app does not immediately start the camera, so i can await a request/release to trigger Android Chrome (and i guess Safari) to ask for permissions first, then do...
yeah npm install @ericblade/barcode-validator, you get the javascript library. UPC-A and EAN-13 are the same thing https://www.nationwidebarcode.com/are-upc-a-and-ean-13-the-same/ You could use it without the barcode-validator package, just remove the references to...
Well, there's a specific list of valid readers, and if you pass in something that isn't valid at init time, then sometime later, you get an error that doesn't appear...
Yep that's the one. I had filed this when I ran across the problem, just for future reference, I hadn't really thought about it at the time ... But now...
Yeah, it should. Dynamically added readers don't seem to be working in LiveStream mode, so that's a problem (and also quite difficult to write a test for, I think, but...
I think the crux of this problem, is that passing invalid reader strings generates a runtime error -- after the fact -- that doesn't point to where the actual problem...