-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
Invariant Violation when passing an object with Infinity into addBreadcrumb
#4024
Comments
Hi @thomasttvo, we recommend adding know data structures to the breadcrumb, but regardless that, the |
|
After running the sample code I'm not getting the same error but malformed JS call. It looks like RN serialization error. |
I believe the malformed JS is caused by RN catching the uncaught error and doing some processing with it. If you wrap it around a try/catch, you'll get the error I mentioned |
Thank you, I did that, but the malformed JS is a native error and is not captured by the JS try/catch. |
…rs (#13406) RN SDK uses the normalize function before passing data over the RN Bridge, which only accepts serializable data. Infinity causes -> getsentry/sentry-react-native#4024
Fixed in https://github.com/getsentry/sentry-react-native/releases/tag/6.0.0 and newer. |
OS:
Platform:
SDK:
@sentry/react-native
(>= 1.0.0)react-native-sentry
(<= 0.43.2)SDK version: 5.29.0
react-native
version: 0.73.5Are you using Expo?
Are you using sentry.io or on-premise?
Calling
addBreadcrumb
on Android with an Infinity value throws an error, which may crash the app in certain cases. We don't usually mean to call it with an Infinity value, but it's hard to control what's being logged automatically.I think at the very least, Sentry should wrap its methods around try/catch internally and log the errors to avoid them affecting the main application?
The text was updated successfully, but these errors were encountered: