You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We wrap certain functions such as certain global event handlers in order to catch otherwise unhandled exceptions that do not necessarily go through the window.onerror handler. This leads to stack traces with what looks like rollbar code causing the error due to the _wrapped method showing up at the top of the stack trace.
Additionally, this makes host whitelisting hard to do for bundled code because that _wrapped frame will usually have a filename that matches the client's bundle because that is where rollbar lives.
The code that does the wrapping should pass information to rollbar.error which signals that the error is being generated within a wrapped function. This can then be used to modify that particular frame in the trace to have something like:
We wrap certain functions such as certain global event handlers in order to catch otherwise unhandled exceptions that do not necessarily go through the window.onerror handler. This leads to stack traces with what looks like rollbar code causing the error due to the _wrapped method showing up at the top of the stack trace.
Additionally, this makes host whitelisting hard to do for bundled code because that _wrapped frame will usually have a filename that matches the client's bundle because that is where rollbar lives.
The code that does the wrapping should pass information to rollbar.error which signals that the error is being generated within a wrapped function. This can then be used to modify that particular frame in the trace to have something like:
The text was updated successfully, but these errors were encountered: