[safari] SyntaxError: The string did not match the expected pattern.
See original GitHub issue- 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.
Issue Analytics
- State:
- Created 4 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
I keep getting the error "the string did not match the expected ...
In this situation Safari once gave me the OP's error, but Chrome was more specific: "unexpected token W in json at position 0"...
Read more >Carson Shold on Twitter: "TIL some versions of Safari throw an ...
TIL some versions of Safari throw an error "SyntaxError: The string did not match the expected pattern" if you don't close your selector...
Read more >Issue - The string did not match the expected pattern
Hello, I am new user of Power BI Desktop. I was looking into learning docs where in this mentioned link.
Read more >The string did not match the expected pattern - Data Collection
The string did not match the expected pattern · Open Chrome · Click to Help · Click About Google Chrome · You should...
Read more >HTML : I keep getting the error "the string did not ... - YouTube
HTML : I keep getting the error "the string did not match the expected pattern " for my fetch request [ Gift :...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub 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
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