-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(integrations): Don't add empty stack trace in RewriteFrames
#5625
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
fix(integrations): Don't add empty stack trace in RewriteFrames
#5625
Conversation
.replace(/^[A-Z]:/, '') // remove Windows-style prefix | ||
.replace(/\\/g, '/') // replace all `\\` instances with `/` | ||
.replace(/^[A-Z]:/, '') // remove Windows-style prefix | ||
.replace(/\\/g, '/') // replace all `\\` instances with `/` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
git is doing those spacing changes automatically, should I leave it as is or return to the original spacing?
EDIT: It seems like vscode enforces the removal of additional spaces where prettier wants the additional spaces.
RewriteFrames
Co-authored-by: Abhijeet Prasad <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @lucas-zimerman!
Hey guys, I'm still seeing this error here. I'm struggling to get my Expo Hermes source maps working properly. This is the issue example. |
This PR avoids adding an empty stack trace when a stack trace is not defined.

By doing that, you'll no longer see the following error message at Sentry:
Fixes #5609 and potentially fixes getsentry/sentry-react-native#2429
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint
) & (yarn test
).