-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Incorrect parsing of frames if a path is in an exception message #5498
Labels
Comments
AbhiPrasad
added
Package: browser
Issues related to the Sentry Browser SDK
Status: Backlog
labels
Jul 29, 2022
Backlogged, but we will look at this soon! Thanks for reporting! |
This was referenced Aug 1, 2022
@billyvg do you have the full It looks like this is hitting the Gecko parser but this is a an error from Chrome. This suggests it was not recognised by the Chrome parser!
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/react
SDK Version
7.8.0
Framework Version
No response
Link to Sentry event
No response
Steps to Reproduce
Capturing this exception:
Leads to this code in the core SDK
where the path in the exception message gets matched with the regex and is mistaken as a frame:
This then gets filtered by inbound filters as it does not match any URLs in
allowUrls
.Expected Result
Frame at index 0 should not exist
Actual Result
As a workaround, I'm wrapping the pathname in quotes.
The text was updated successfully, but these errors were encountered: