sentry-javascript: [safari] SyntaxError: The string did not match the expected pattern.

Review the documentation: https://docs.sentry.io/
Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
Use the latest release: https://github.com/getsentry/sentry-javascript/releases
https://sentry.io/organizations/kalo/issues/1544639144

Package + Version

@sentry/browser
@sentry/node
raven-js
raven-node (raven for node)
other:

Version:

5.14.0

Description

After updating to 5.14.0, I had reports come in about errors not seen before.

next.js error report w/ the same message, (and related fix) which refers to the Performance API in the browser, which raised the same kind of error.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 19 (7 by maintainers)

Most upvoted comments

@ValentinH @ipa1981 ah, nvm. My bad, I completely misread the issue (I thought it’s a different one I was working on).

So apparently this is the old Safari (notice that events are using iOS 10/11) issue when DOM selector is malformed, see: https://www.reddit.com/r/firefox/comments/5nbmqi/on_handling_invalid_selector_strings/

We are not querying DOM ourselves in any way, so it’s not originating from our codebase. Unfortunately, DOMError doesn’t contain any additional information about it, so we’re not able to tell which selector was malformed - https://developer.mozilla.org/en-US/docs/Web/API/DOMError

kamilogorek on Jul 7, 2020

Have the same issue. SDK: sentry.javascript.browser 5.15.5 User-Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 12_4 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/81.0.4044.124 Mobile/15E148 Safari/604.1 OS: iOS 12.4 Browser: Chrome Mobile iOS 81.0.4044

Kyr on Apr 30, 2020

@olleolleolle Can you update to 5.14.1 I hope this is fixed there.

HazAT on Mar 12, 2020

@kamilogorek Hi, I’m getting this error with "@sentry/react": "^5.27.1" but the solution you linked is not related to my issue since I’m not using a DOM selector in my codebase. Is there another possible reason I’m receiving this error? This is happening with Safari 12.1.2

gigiskarlett on Nov 2, 2020

Thank you really much for the details. Now I understand this error 😃

ValentinH on Jul 7, 2020