hi, we installed sentry to supertokens node backend to figure out issues some users are having about google login and capture some errors happening. looks like google apis are failing and it is happening quite often. can someone tell why this is happening?

hey @bian do you have any error stack for these?

yeah, actually uploaded before once.

since how many days is this happening?

i think this has been happening since forever as users were constantly reporting google login sometimes fails on first attempt.

i see.

could capture yesterday trying to find out issue with thirdparty user id changing.

So usually, we see this type of error only if the signinup API is getting called twice in a row where the second call fails cause google rejects the reuse of an auth code. This usually happens cause of an issue on the frontend side. Do you think this is happening?

in that case, it should reject with some error codes not just timeout, no?

Yes. That’s true.

oh, yeah. about 400 error codes. this is inside response.

data: { error: 'invalid_grant', error_description: 'Bad Request' }

right, so that happens when the API is called twice

so this can happen when we make calls twice with same code?

yea

customized UI but most of part is the same as pre-built UI...

right. The part that's calling the signinup API on the frontend, is that from our pre built UI or custom UI?

we did some customizations like showing popup instead of redirect.

hmm.

so when is this api POST https://oauth2.googleapis.com/token called exactly?

so first, google redirects to the frontend which calls the signinup API expsosed by our backend SDK middleware. That API, calls the google's token endpoint.

so possibility is - frontend on callback url is double-calling signinup api, maybe?

yup

okay, i will check on that.

that would cause the 400 error that you see. But im not sure about the timeout one. If you find out the cause of that, please let us know 🙂