Getting Error in Console response “Uncaught (in promise) Timeout”

[nisargrthakkar]

In the console, I am getting the following error

[BramDecuypere]

Having the same issue! Were you able to solve it? @nisargrthakkar

I found out it only happens when I'm throttling to a very low speed. But we already had 84 occurences in PROD in the last 10 days.

[nisargrthakkar]

@BramDecuypere No, We are facing the same issue. In Google ReCaptcha issue is open google/recaptcha#269.

Personally, I don't think this issue is not related to low speed.

[blindfish3]

@nisargrthakkar - throttling and network conditions are absolutely at play here. There's an unhandled timeout in Google's recaptcha code; and no easy way to handle it from outside. If a timeout occurs - most often because of temporary network failure on the client end - the uncaught promise is logged.

I know this because I was tasked with dealing with the many Sentry errors this was generating on a React application. IIRC I had to suppress them in Sentry :/

[trickydisco78]

Looks like someone has found a fix for this

google/recaptcha#269 (comment)
https://gist.github.com/ANTOSzbk/75ed7003e914162550f61399122a3bd4

Could this be implemented?

[npearson72]

I've noticed that is not happening in production / without React strict mode. Can anyone else confirm?

[Zues-12]

I've noticed that is not happening in production / without React strict mode. Can anyone else confirm?

Nope, still happens to me

[ltmervin123]

I face the same issue when the ReCAPTCHA from react-google-recaptcha is rendered for a long period of time, even if it generates a valid token.

How do you guys resolve this issue?