Hi I'm using supertoken with node-fastify and react on front end. I'm getting a wired error on

thirdPartySignInAndUp

function. This is the error {type: 'cors', url: 'http://localhost:20070/auth/signinup', redirected: false, status: 500, ok: false, …}

Hey @undesiredmonk

This is the error on the network tab

Ah ok. So it seems that there is some issue in the social login config.

Been stuck on this for some time. Would appreciate a help.

Sure. A few things to check: - Make sure the provided clientId and secret are correct. - Make sure that if you have given custom scope, it includes email. - If you are making any customisations to signInUp API or have made a custom provider, then show us the code here. - Make sure that the redirect URL configured on the provider's dashboard is correct.

- Client ID and secrets are correct. The redirect URL is called. - No customizations or to signInUp API, Its happening with Google login

alright. So let's wait for @sattvikc to help here.. he will be available tomorrow.

Anything I could have missed. I'm working with a strict deadline.

nothing obvious it seems. One thing to try is that you can use our dev google credentials (in the docs) and does it work with that?

Can you share the link?

https://supertokens.com/docs/thirdpartyemailpassword/pre-built-ui/setup/backend -> you can find the credentials in step 3.

The wired thing is I'm getting the user details. Even though there is an error.

hmmm interesting

backend http://localhost:20070/auth/signinup

wait.. but the previous screenshot says request failed with 500

yes

thats very weird

fastify

how? Can i see the code?

Give me a moment. I'll check it once throughly.

can you hardcode the origin instead of using config.appOrigin[0]?

Was able to resolve the issue. Looks like the plugin was not properly registered.

Ah. The CORS one or supertokens one?

Yes.

Which one?

@rp This

Was there an issue in our docs about it? Or something else?

It was my mistake. Somehow I had two instance of fastify registered.

Hmm. I see. Ok!

Thanks for the help. Sorry to bother you with my silly mistake.