Moti Zilberman 56f08fcf84 Pop bridge frames from errors thrown by sync host function calls ...

Summary:
When a synchronous call from JS to native code throws an error, it doesn't include a useful stack trace from the native side. To improve error attribution, this diff pops the frames in `MessageQueue.js` and `NativeModules.js` from the stack traces of such errors. This uses the `error.framesToPop` convention understood by RN's global error handler.

For now we limit this to errors converted from C++ exceptions in host functions, since those are not likely to ever contain further JavaScript frames at the point where we catch them; if they did, it would violate our assumption that the top two frames of the stack are in the JS bridge code.

Reviewed By: cwdick

Differential Revision: D15805054

fbshipit-source-id: 8c1dd7c81b00b6a88e31473271889af1f88f7263

2019-06-19 09:15:14 -07:00

..

__mocks__

Add test for sync methods (type=sync)

2019-06-19 09:15:14 -07:00

__tests__

Pop bridge frames from errors thrown by sync host function calls

2019-06-19 09:15:14 -07:00

BatchedBridge.js

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

MessageQueue.js

Pop bridge frames from errors thrown by sync host function calls

2019-06-19 09:15:14 -07:00

NativeModules.js

Preserve the caller's JS stack trace when a type=promise method rejects

2019-06-19 09:15:14 -07:00