Hi, I'm trying to implement supertokens into my nestjs + nextjs application with ThirdPartyEmailPassword. I encountered an error when trying to signin/signup with Google. The account is successfully signup/signin in the development environment but the /signinup api failed with status code 500 on frontend 400 on backend, then the error got displayed on the form. When reload the frontend application, it does recognize that I've logged in and redirect to the home page tho.

hey @howard can you please enable debug logging and show the logs on app start + when you make the API call that behaves weirdly.

here is the debug log.

thanks.

here is my supertokens.service.ts

hmm this seems about fine

yeah, I see that it still work afterwards. Can I skip the /signinup api call?

You can't skip it. Can you try this:

let google = ThirdpartyEmailPassword.Google({...});

providers: [
                {
                    ...google,
                    get: function (redirectURI: string | undefined, authCodeFromRequest: string | undefined, userContext: any) {
                        const getResult = google.get(redirectURI, authCodeFromRequest, userContext);
                        return {
                            ...getResult,
                            getProfileInfo: async function (authCodeResponse: any, userContext: any) {
                                try {
                                    const result = await getResult.getProfileInfo(authCodeResponse, userContext);
                                    console.log(result); //<- this one has my login details (id, email, verified)
                                    return result;
                                } catch (err) {
                                    console.log(err);
                                    throw err;
                                }
                            }
                        };
                    }
                },
            ],

yeah, I am

Ah yea.. so in nextjs, weirdly, they call

useEffect

twice in development mode when react strict mode is enabled

oh, the first signinup request is not the POSR request

so it's calling the API twice

it got canceled and only contains the headers

Can you try to run this in a production build or without react strict mode?

ok, I'll try it in the morning. Now it's 1 am in my place tho

ah alright!

thank you, I'll notice you later if there's a problem

do lmk if it solves the issue

The production build worked!

Yea! I opened an issue about this in nextjs: https://github.com/vercel/next.js/issues/36233

thank you! hope it will be resolved soon

yup! me too.. i was surprised that this wasn't an open issue already.. very strange