mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
9baf6f2140
Summary: JSError creation can lead to further errors. Make sure these cases are handled and don't cause weird crashes or other issues. This solution has a few parts: * include a ScopedNativeDepthTracker in checkStatus * If an exception object message or stack property is already a String, don't call JS String ctor on it * Verify that a jsi::Value is a String before calling getString on it. * Add more tests for JSError construction Changelog: [Internal] Reviewed By: dulinriley Differential Revision: D21851645 fbshipit-source-id: 2d10da0e741ad4ede93cd806320f68ad512e5138