UnhandledRejection: "error". According to the analytics service, this is expected behavior.
Since the calls are made from deep within the 3rd party library, we can’t wrap them in try-catch directly. Sentry makes it seem like the errors are coming from our website, since we load the 3rd party library directly, so adding the URL to the blacklist isn’t possible.
UnhandledRejection: "error" is generic enough that I don’t want to add that string to our
ignoreErrors array, either.
Is there a way to filter based on what the promise that had an
unhandled rejection was trying to do?