Christina Holland

You can just provide a repo that contains the code that causes the problem, and link it here, and let us know to run the code in a production environment....

Thanks. It looks like Node support for Crypto.getRandomValues() is fairly recent (Node 15) so if we update to it, we'll probably want to make sure we wrap it in a...

I'm still not sure about the first error, but the second error doesn't seem to be related to the SDK itself, it seems like all the errors in the stack...

I'm not sure if we can prevent the 403 itself, if the problem is that reCAPTCHA doesn't work after a long sleep, but it shouldn't be making that many repeated...

Someone is looking into why throttling isn't working. It would be great to catch if ReCAPTCHA has gone wrong after a long sleep, and reload ReCAPTCHA if so. Unfortunately, due...

This is merged and should be released this week, usually Thursday. This will only fix the throttling issue and prevent too many requests to the endpoint which all return 403....

No, that would cause it to not work at all in the first place. Thanks for filing a separate issue, will address it there.

Sorry, still looking into this. I think there's something wrong with the refresh timing. As a workaround you may be able to initialize app check with the `isTokenAutoRefreshEnabled` option set...

I just finally looked at your gif above, and it seems to show repeated auth requests? Like the app is repeatedly logging in the user? I know you said you...

This seems to be the only PR added in the 9.8.4 release, I'm not sure if anything in that would cause this effect. https://github.com/firebase/firebase-js-sdk/pull/6273