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
### Description
Upgrade sentry/react-native from 1.7.1 to 2.1.0.
This is part of our effort to improve debugging capabilities. With this update we hope to see better stack traces in some native crashes where the entire trace is missing.
I went through the release notes for each of the releases since 1.7.1 to make sure we capture any breaking changes and to see what has been fixed and what to watch out for.
One thing that has been added is release health which we should discuss whether we want on or off: https://blog.sentry.io/2020/05/19/crash-free-sessions-carefree-users-with-release-health
What's new in sentry:
- Bump sentry-android to 3.2.0 getsentry/sentry-react-native#1208
- Fix: set userId for hard-crashes if no user is set [#1049](getsentry/sentry-java#1049)
- Bump @sentry/javascript dependencies to [5.28.0](getsentry/sentry-react-native#1228)
- Bump sentry-cocoa to [6.0.9](getsentry/sentry-react-native#1200)
### Other changes
Set sentry automatic session tracking explicitly off because the default has changed in 2.0. Not sure yet if we want that on so I set it off to be explicit.
### Tested
Manually causing crashes in JS:
`throw new Error("My first Sentry error!");`
and in native:
`Sentry.nativeCrash();`
### Related issues
- Fixes#6203
### Backwards compatibility
Yes.
Expected Behavior
Good stack traces that are actionable.
Current Behavior
Some of the stack traces have little information or just say "undefined" and I think sentry has made some fixes recently.
The text was updated successfully, but these errors were encountered: