-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[iOS] crash in facebook::react::Value::toJSONString #22682
Comments
Possibly! I believe the published version is on 0.57.5. everyone will get 0.57.8 in our next release though. I'm inclined to believe it's a different bug because #16099 is the exact same issue as mine but opened a year ago, whereas the ones you pointed to were recently introduced changes. (The bot told us to open a new issue if it was still happening). |
I'm facing the same issue on |
Any workaround ? |
I'm only getting it for a couple users in prod, so I haven't been able to figure it out |
I'm getting a really similar crash report, also only on production, but on android devices. UPDATE: I created a stackoverflow post with more details. Log
|
@noahtallen did the update to 0.57.8 resolve the issue for you? |
hmm.. We're on 0.59.8 now. Looking through our crash reports, I don't see any recent reports of this issue. Perhaps it's fixed! I was never able to reproduce it, so I can't say for sure. I think I'll close this issue then? Let me know if I should reopen it. |
Thanks @noahtallen - that gives me hope :) |
I'm facing the same problem, any workarounds? |
RIP. I never figured it out. I'm assuming you're on the latest version? If so, I'll reopen |
I |
Environment
Description
In production, our app is getting a crash. (I believe react-native version for the published version which got the crash is 0.57.5).
Device information:
iPhone 6 on iOS 11.0.3
Available Storage: 21.26 GB
Available RAM: 123.89 MB
Here is the overview from Crashlytics:
Here's the entire log
My guess is that our redux state is large enough that there was not enough available RAM to persist it over the bridge via redux-persist. But I'm not 100% on that. It seems really likely, though, considering all the information on the issue I have linked below:
I'm not sure what the solution should be for this issue. I think there should be some sort of feedback when this sort of situation arises, at least. Some mentioned that it is possible to chunk large strings up into smaller values to conserve RAM, though if that is necessary it should probably happen in react-native itself. If anyone could point me to the source code where this would be an issue, I would be willing to investigate further and potentially submit a PR.
Reproducible Demo
I have been unable to reproduce this issue in development mode. However, there is a lot of context about it in this identical issue which was closed a while ago due to it being an old version of react native.
The text was updated successfully, but these errors were encountered: