react-navigation non-serializable state recursive call to `dropUndefinedKeys`
See original GitHub issueEnvironment
sentry.io
"@sentry/react-native": "^2.4.0"
react-navigation
Steps to Reproduce
- Pass a circular object as a
param
to a navigation call
Expected Result
Navigation successful, something’s logged in Sentry
Actual Result
RangeError, call stack size exceeded in dropUndefinedKeys
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (9 by maintainers)
Top Results From Across the Web
non-serializable values were found in the navigation state ...
when I enter screen B a warning appears: non-serializable values were found in the navigation state. how can I solve it? reactjs ·...
Read more >State persistence | React Navigation
Each param, route, and navigation state must be fully serializable for this feature to work. Typically, you would serialize the state as a...
Read more >VS Code API | Visual Studio Code Extension API
VS Code API. VS Code API is a set of JavaScript APIs that you can invoke in your Visual Studio Code extension. This...
Read more >The redux best practice "Do Not Put Non-Serializable Values ...
This article explains one of the four react-redux best practices: "Do Not Put Non-Serializable Values in State or Actions"
Read more >JSDoc: Source: fabric.js
Calling this method * without arguments removes all handlers for all events ... __eventListeners) { return this; } // remove all key/value pairs...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jennmueng can you take a look at this, thanks.
Closed in favor of https://github.com/getsentry/sentry-javascript/issues/4777