-
Notifications
You must be signed in to change notification settings - Fork 979
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No results from the scanner on > iOS 14 #486
Comments
I'm told that selecting an aspectRatio: { ideal: 1 } in your constraint works there, although I can't confirm that since I lack any iOS devices. |
Thank you @ericblade |
just realized it's aspectRatio: { ideal: 1 } .. might take a look through this thread for some ideas ericblade/quagga2#419 |
Thank you. I tried this configuration. Still not working properly. The iPhone camera appears to be incredibly picky. I scanned one EAN code succesfully, which had nearly the exact camera format. As soon as some text is around the EAN, or the EAN is quite small and can not be recorded in the camera's format due to exceeding the minimum focus distance of the iPhone's camera, the scanner always fails. On the other hand, Android scans EANs without any problems, even if they are not in the camera format, surrounded by text or very small. So would you suppose that this is an issue related to the library (The iPhone camera itself works perfectly, focusses correctly) or due to Safari/iOS? |
I wish I had any more insight to that. The control that a web app has, and more so on iOS, compared to a native app, over the camera functionality is pretty minimal. It could be hardware, it could be OS/Browser, or it c ould be the library. Could be a combination of all of that just not working together in expected ways that work elsewhere. :| |
does you fixed it? i have same issues, this beacause onProcessed() function run only one time when init. So it never get onDetected() |
@JonSnow-vn |
yes, me too, this problem only on iphone. Like what i say, on iphone, onProcessed() function run only one time when init. I test on macbook pro and ipad pro its work fine. I don't konw ipad mini is work? i dont have this. |
Interesting observation, I have not debugged it that in-depth. |
you have any idea? |
Unfortunately, I don't. The one person using my app on iOS isn't reporting any problems. |
I can confirm, is working fine here. |
Anyone have any other ideas to resolve this? I'm still unable to scan on my iPhone 13 mini after messing around with setting aspectRatio. |
Is this issue resolved? |
@PriyaN-d Yes, we were able to get this working again last year - though we did have to add a way for users to try out each available camera themselves (different models expose different settings/lenses, front/back/wide angle etc...) |
this is probably the way. On a lot of Android devices, the default camera selection provides fisheye view, which mangles the image |
The scanning functionality of Quagga stopped working. I tried different aspectRatios and different configurations regarding the camera selection without any success.
The camera selection, on the other hand, and general implementation work fine – the stream starts without any issues. No barcodes (ean_code) are recognized though.
Android works without any issues.
Test device: iPhone 12 Pro
The text was updated successfully, but these errors were encountered: