Skip to content
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.

Sign up for GitHub

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

Jump to bottom

System requirements? #17

Closed
idegart opened this issue Jan 24, 2018 · 1 comment
Closed

System requirements? #17

idegart opened this issue Jan 24, 2018 · 1 comment
Labels
question

Comments

@idegart
Copy link

idegart commented Jan 24, 2018 •
edited by gruhn

I'm tried to use this component but it doesn't work on my iPhone 5 v.10.3.2

What is system requirements for this component?

There is error from your site:
jxzoqmblq6y

This error in Safari and Chrome(newest)
@gruhn
Copy link
Owner

gruhn commented Jan 24, 2018

Short answer: it only works on iOS 11 😞

The error message tells you that WebRTC is not supported. This is a relatively new Web API and the one we need to access a users camera from the browser. Apple first implemented it in Safari for iOS 11. Apple forces all browsers on iOS to use Safaris WebView component and doesn't allow them to implement their own. That's why, it doesn't work with Chrome either (and it won't with Firefox and so on).

The only alternative to WebRTC would be an implementation with Adobe Flash but since Apple never supported that either, there is no chance to have this component working on iPhone with iOS 10 and below.

@gruhn gruhn added the question label Jan 24, 2018
@gruhn gruhn closed this as completed Jan 25, 2018
@gruhn gruhn mentioned this issue Jan 25, 2018
Closed
@gruhn gruhn mentioned this issue Mar 9, 2018
Closed
gruhn added a commit that referenced this issue Apr 6, 2018
@gruhn
Refactor according to jsQR upgrade
240950f 
jsQRs official API has no dedicated functions for locating and decoding
anymore. There is only one general purpose function that handles both.
Therefore no need to deal with those cases separately anymore.

This also allows removal of the event-listener-reqistered condition,
assuming that at least a `decode` or `locate` listener is always
registered. Implicitly this should resolve #17 too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@idegart @gruhn