chobo2

> 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...

this is what I added with the release and request ones. ``` Quagga.CameraAccess.request(null, {}).then(function() { Quagga.CameraAccess.release().then(function() { Quagga.CameraAccess.enumerateVideoDevices().then(function (devices) { init(devices) }); }) }); ```

> 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...

> 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...

> 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,...

> If it works on everything other than a specific iOS device, I'd point at that being either a problem with that version of iOS, something with that hardware, or...

Hey Thanks for that write up, When I read about it, it does make sense till I get back to my application again. Where I have a scenario like this....

> instead of running > `component={withTracker(SearchableComponent)}` > try somewhere define > `const searchableComponentWithTracker = withTracker(SearchableComponent)` > and later > `component={searchableComponentWithTracker}` > > other way is in SearchableComponent.jsx use > `export...

> There's a new docs issue on this subject at: [dotnet/AspNetCore.Docs#31402](https://github.com/dotnet/AspNetCore.Docs/issues/31402) > > There are at least a couple of PU issues that seem related to this ... > >...

I seem to only be getting this issue when I try to use my template in VS 2022, when I use the cli it seems to work proper.