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.

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

[BUG] Safari 14 requirement on desktop not detected #282

Closed
janbrasna opened this issue Oct 10, 2021 · 10 comments
Closed

[BUG] Safari 14 requirement on desktop not detected #282

janbrasna opened this issue Oct 10, 2021 · 10 comments
Assignees
Labels
bug Something isn't working Next release Things that are done and will be part of the next release and close automagically at this time

Comments

@janbrasna
Copy link
Contributor

janbrasna commented Oct 10, 2021

What happened?

After successfully recognizing a QR on camera, the app stops on unhandled promise rejection. ReferenceError in @cbor/lib/constants.js as in the screen shot attached.

What browsers are you seeing the problem on?

Safari (desktop 13.1.3)

Are you browsing using

a computer (macOS Catalina 10.15.7)

Anything else?

Screen Shot 2021-10-10 at 23 01 35

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.3 Safari/605.1.15 https://www.whatismybrowser.com/w/9F68GL4

@janbrasna janbrasna added the bug Something isn't working label Oct 10, 2021
@github-actions
Copy link

Hey there 👋🏼 Thanks for your first issue. This is an automated message but a real human will handle your issue very shortly.

@janbrasna
Copy link
Contributor Author

Ah, okay, the app only works in Safari 14+ … however I didn't run into any error message stating so, as is described in #54 (comment) 🤷‍♂️

@clawfire
Copy link
Owner

Hey there 😃
It needs safari 14+ on mobile, we never tested the minimal requirement on desktop 🤔

@github-actions
Copy link

This issue seems to be a little bit old and no ones seems to be able to help 😕. Or waiting for more informations from the reporter ⏳. If no new activity, It will be closed in 5 days

@clawfire
Copy link
Owner

clawfire commented Nov 1, 2021

That's weird, you should have seen a message. However, there's no feature detection mechanism for bigInt I know, so I need to rely on parsing the userAgent, which is not always reliable to guess which version you are using :/

@clawfire clawfire changed the title [BUG] Unresolved promise from cbor [BUG] Safari 14 requirement on desktop not detectexd Nov 1, 2021
@clawfire clawfire changed the title [BUG] Safari 14 requirement on desktop not detectexd [BUG] Safari 14 requirement on desktop not detected Nov 1, 2021
@clawfire clawfire self-assigned this Nov 1, 2021
@clawfire clawfire added the Next release Things that are done and will be part of the next release and close automagically at this time label Nov 1, 2021
@clawfire
Copy link
Owner

clawfire commented Nov 1, 2021

A fix is on its way 😃

clawfire added a commit that referenced this issue Nov 1, 2021
* release/2.2.0:
  Bump version number
  Fixes #282 : add detection support for Safari < 14 on desktop
  added default tz into formatDate
  updated ua-parser-js (security issue)
  Add CZ instructions
  Bump version number and write changelog
  Last minute language fix
  Handle when we don't decode any relevant data
  URL detection for #126
  Remove 💀 dead code
  Add function documentation
  Trying to put some orders on where to define what
  Fixes #23 : Ask the device for environment camera if available
  Updating libs
  router fix
  Fixes #152 central date string management
  Issue #125 Implement Apple's ignore timeZone instruction
  Forgot that one here it remove the urn pattern
  Fix when urn:uvci is lowercase
@janbrasna
Copy link
Contributor Author

Ah, gotcha! I see it now. However, that doesn't work as

$.ua.browser.version < 14 compares a string e.g. "13.1.3" so that's false anyway:

Screen Shot 2021-11-02 at 18 37 29

Maybe a parseFloat() would be the right choice? As:

Screen Shot 2021-11-02 at 18 37 55

I'd propose a PR however you'd prolly want to test it more than my code smell knowledge goes…;]

@clawfire
Copy link
Owner

clawfire commented Nov 2, 2021

hum. Can't really use parseFloathere because 13.1.3 will be converted into 13.1 I guess (hope).
I'll have to check, the ua-parser should have a method for that.

@clawfire clawfire reopened this Nov 2, 2021
@janbrasna
Copy link
Contributor Author

@clawfire Yup, it parses 3.14whatever to 3.14 just fine… which is good enough for this major version comparison needed I guess. But I'd rather let that to whatever is your liking, algorithm-wise;)

@clawfire
Copy link
Owner

clawfire commented Nov 5, 2021

@clawfire clawfire reopened this Jan 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Next release Things that are done and will be part of the next release and close automagically at this time
Projects
None yet
Development

No branches or pull requests

2 participants