Errors in Chrome Extension Message Handlers not Logged

Package + Version

• @sentry/browser

Version:

5.5.0

Description

I am using Sentry to instrument a Chrome Extension. For the most part this works well.

However, uncaught errors in listeners registered via:

chrome.runtime.onMessage.addListener

are surprisingly not logged by sentry.

Note that uncaught errors in these handlers have a slightly different form when printed to the console. A normal uncaught error might log like this:

Uncaught TypeError: XYZ

While errors in the onMessage handler log something like:

Error in event handler: TypeError: XYZ

[kamilogorek]

@scottfr async messages are not bubbling up to the main onerror listener, as they are meant to be used in communication between channels.

Your best bet here (which works just fine, tested it locally) is to use Sentry.wrap

chrome.runtime.onMessage.addListener(function(request, sender, sendResponse) {
  Sentry.wrap(function() {
    throw new Error(
    "I am an error registered in an onMessage handler. I will incorrectly not be logged to sentry. You will still see me in the console."
    );
  });
});

[scottfr]

OK, sounds good. Thanks for looking into this.