App Crashes with NSInvalidArgumentException Invalid number value (infinite) in JSON write #3421
Closed
4 of 11 tasks
Assignees
Labels
Comments
github-project-automation
bot
moved this to Needs Discussion
in Mobile & Cross Platform SDK
|
Exception traces from XCode 
|
|
We added this to the setup code for now to disable breadcrumb And that seemed to fix the issue for us. The other thing to call out is that our repro step (e.g. that specific image upload flow we have) would:
So I assume this issue is actually related to #2744, even though it seems like nobody but us are having the issue in the release build. |
|
Hi, thank you for the message and details, Just to make the investigation scope smaller, do you manually add some breadcrumbs in your RN code? |
No we are not creating breadcrumbs manually. And I assume the Stream SDK library isn't doing that either. |
getsantry
bot
added
Waiting for: Product Owner
and removed
Waiting for: Community
labels
getsantry
bot
moved this from Waiting for: Community
to Waiting for: Product Owner
in GitHub Issues with 👀
7 tasks
|
Based on the Stack Trace it looks like serializing a Breadcrumb created by the RN SDK failed in |
krystofwoldrich
moved this from Needs Discussion
to Needs Review
in Mobile & Cross Platform SDK
github-project-automation
bot
moved this from Needs Review
to Done
in Mobile & Cross Platform SDK
|
@krystofwoldrich can I assume to find the fix in the @sentry/react-native: 5.15.1 version or how is it handled? I'm a bit confused since the fix you mentioned was merged into the getSentry/sentry-cocoa package. Since it is a serious production issue, I'd be happy about your fast reply, thx! :) |
|
Hi @Arashadmin! The fix is part of sentry-react-native 5.15.0. The fix on the iOS SDK was part of the |
1 task
|
This seems to have fixed the problem on iOS. However, for Android, now I am getting the issue described in #2744. I was only able to test a non-release Android build though (since I don't have the signing key for our app), so it is possible that the #2744 issue isn't reproducible on release build, per the discussion in #2744. |
|
@tao-qian #2744 was fixed in PR #2852 which is part of release 5.15.0 - so the issue should not come up with this version. Please note that you need to rebuild the native app for the fix to be effective. If this doesn't work and you can reproduce the issue in develop mode, please follow up by creating a new issue referring to this conversation - thank you! |
|
@kahest release 5.15.0 is not yet available for expo users, see here: https://github.com/expo/sentry-expo/blob/main/CHANGELOG.md#master:~:text=%F0%9F%A7%B9%20Chores-,7.1.1%20%2D%202023%2D10%2D18,-%F0%9F%8E%89%20New%20features . 5.10.0 is the latest supported version there. I turned off Sentry until it is available due to prod crashes |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OS:
Platform:
SDK:
@sentry/react-native(>= 1.0.0)react-native-sentry(<= 0.43.2)SDK version: 5.14.1
react-nativeversion: 0.71.4Are you using Expo?
Are you using sentry.io or on-premise?
If you are using sentry.io, please post a link to your issue so we can take a look:
https://brightgo-inc.sentry.io/issues/4646869833/?project=4504906435330048&query=is%3Aunresolved&referrer=issue-stream&statsPeriod=1h&stream_index=0
Configuration:
(
@sentry/react-native)I have the following issue:
App would crash with NSInvalidArgumentException Invalid number value (infinite) in JSON write.
Steps to reproduce:
This is reproducible consistently for us in a particular user flow of sending images while offline. See GetStream/stream-chat-react-native#2326 where we reported the issue to Stream (the chat SDK we are using) initially.
I assume a specific non-Sentry error was triggered during that user flow, and while Sentry is trying to handle the error, it causes the crash.
Actual result:
Our app would crash.
The text was updated successfully, but these errors were encountered: