fix(core): avoid crash on logging circular objects #5186
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
safeStringifyfunction was added to fix #4506, but didn't do it properly as there is a follow up PR that is still unmerged. And also causes a crash on iOS apps if you try to log an object with circular references, see this issue for more details.Since we changed the way the console overwrite works on iOS, looks like the
safeStringifyis not even needed, so this PR removes it. After merged, circular objects that error onJSON.stringify()will go back to printing[object Object]as they did before thesafeStringifyPR was merged instead of crashing the app.closes #5178
closes #4573