Sentry-javascript: UnhandledRejection: Non-Error promise rejection captured with value: Timeout

We had multiple issues like this and pinned it down to google recaptcha code. It is very flaky, so we got rid of recaptcha and errors disappeared

@JustFly1984 Thanks for the confirmation. Recaptcha is my prime suspect. Unfortunately we cannot remove it. Looks like it maybe doesn't unmount properly. Still feels like we should be able to get more info from the exception though.

I’ve failed an issue in google bug tracker, but they don’t give a sheet

@JustFly1984 Yep. That's Google for for you. No sheets given.

The issue lies exactly there: https://www.gstatic.com/recaptcha/releases/P6KLRNy7h3K160ZmYNUOAce7/recaptcha__en.js

c.reject("Timeout ("+y+")")

or

H((vn.delete(P),"Timeout")

tl;dr - they reject with a primitive value, but should with new Error("timeout").

In this case, your best solution until they fix it is to ignore this kind of errors.

Sentry.init({
  beforeSend(event, hint) {
    if (hint.originalException === "Timeout") return null;
    return event;
  }
});

@kamilogorek Thanks. Interested why you would filter this out in beforeSend on the client rather than just ignoring in the dashboard?

Because this error is too generic. Too easy to get a false positive match.
Also, I've never seen this exact Timeout error before :D

@kamilogorek Yeah. I guess my concern is that filtering it out on the client might end up masking important errors. At least if you ignore it on the dashboard you still have the data stored.

@Undistraction filtered events are dropped for the end user. Otherwise, they'd count toward quota.

@kamilogorek Ah. I hadn't considered quota. Thanks for clarifying.

Does anybody know how this timeout affects end users?

Closing the issue, as it seems like the original issue has been partially resolved or there is a working solution. I'd prefer someone to create a new issue with a fresh description if it's still an issue.
Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it.
Cheers!

@kamilogorek so this timeout issue is not affected to end users and it is good solution to ignore this one?

It depends on how your codebase is tied to the ReCaptcha SDK, but I'd say that in general, in most cases yes, it shouldn't affect the end outcome.