You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have following issue:
When a native crash happens, the stacktrace is all in one long line, and not formatted correctly.
It's not very useful, as we need to do the extra step of parsing it before we can see where the problem was.
Steps to reproduce:
yarn install
open ios/SentryBadStack.xcodeproj
switch to SentryBadStack Release scheme
yarn start
press play on xcode
tap CRASH JS button
see everything is nice
tap CRASH NATIVE button
see that the stacktrace looks weird, no formatting
@HazAT Actually, I just checked again a bit more carefully. with deactivateStacktraceMerging: false, the native errors are not even reported! I was seeing the old ones before and thought they are the same. In my account, I deleted all the issues and tried again. Only js crashes are reported. That's even weirder. Can you reproduce it with my example repo?
I am closing all old issues, please if this is still a problem feel free to revive it.
Also, consider moving to our new SDK @sentry/react-native if it still happens there please open a new issue.
OS:
Platform:
Output of
node -v && npm -v && npm ls --prod --depth=0
Config:
I have following issue:
When a native crash happens, the stacktrace is all in one long line, and not formatted correctly.
It's not very useful, as we need to do the extra step of parsing it before we can see where the problem was.
Steps to reproduce:
yarn install
open ios/SentryBadStack.xcodeproj
SentryBadStack Release
schemeyarn start
CRASH JS
buttonCRASH NATIVE
buttonrepro repo: https://github.com/pvinis/SentryBadStack
Actual result:
Expected result:
Something more like
The text was updated successfully, but these errors were encountered: