If it's still not working, perhaps you can share your code.

If I have an existent user who signed up with email+password using email

x@example.com

and then I have a sign-up attempt using Github social login for a Github user that has that same email

x@example.com

, is it understood as the same user and just logs in? Anyway, I tried

handlePostSignIn

as well and apparently it isn't being called either. Here is my backend config:

let backendConfig = () => {
  return {
    supertokens: {
      connectionURI: process.env.SUPER_TOKENS_CONNECTION_URI,
      apiKey: process.env.SUPER_TOKENS_API_KEY,
    },
    appInfo,
    recipeList: [
      ThirdPartyEmailPasswordNode.init({
        providers: [
          GithubNode({
            clientSecret: process.env.GITHUB_CLIENT_SECRET,
            clientId: process.env.GITHUB_CLIENT_ID,
          }),
        ],
        signUpFeature: {
          formFields: [
            {
              id: 'userSlug',
            },
          ],
          handlePostSignIn: async (user, context) => {
            console.log('>>> SIGN IN', user, context);
          },
          handlePostSignUp: async (user, context) => {
            console.log('>>> SIGN UP', user, context);
          },
        },
      }),
      SessionNode.init(),
    ],
    isInServerlessEnv: true,
  };

> is it understood as the same user and just logs in? No. It will be two different users. So the first time you sign up with github for a user, you should get the

handlePostSignUp

call. Else the sign in one. For

handlePostSignIn

, you need to put it in the

signInFeature

config. No the

signUpFeature

config.

Ok, I'll try that laters. Thanks for the help!

@User I am getting 401 unauthenticated from the

Session.verifySession()

middleware. How can I troubleshoot this?

Doing something like this

app.use('/api/user', Session.verifySession(), userRouter);

@User - Does the message say unauthorized or try refresh token? - Are the cookies (sIdRefreshToken, and sAccessToken being sent in the request?) - Have you added fetch / axios interception on the frontend when querying this API?

The message says

unauthorized

, I am intercepting the request with axios on frontend. I am checking if the tokens are being sent right now

alright. lmk

Seems the cookies are not being attached, looking into it

alright.

@User if the cookies are not being attached, you could have the following issues: - You have not specified the correct apiDomain in backend / frontend config. - Do you see any browser console output after a successful login response that indicates some error in cookies being attached? - Do you see "Set-Cookie" response headers on a successful login response?

It's working fine now, but an issue I just faced was it returned 401 unauthorized again, and logging in and out fixed it though

hmmm.

The only way that can happen is if the cookies were cleared manually or the session timeout was made short such that it expired.

Hello! I've just upgraded

supertokens-node

and

supertokens-auth-react

and auth stopped working. When I go to

/auth

route, it starts sending lots of

/refresh

requests.

Any ideas what I'm doing wrong?

I didn't change anything in configs, just upgraded modules. As I understand only csrf option was changed In the new version. I don't use csrf explicitly, only

cookieSameSite

option. Not sure what else I could miss..

@User can you see if site cookies have this key called IRTFrontend?

also, please try running

npm update

and try again.

can I also see your frontend config please?

@rp here is the config

export let frontendConfig = () => {
  return {
    useReactRouterDom: false,
    appInfo,
    recipeList: [
      ThirdPartyEmailPasswordReact.init({
        signInAndUpFeature: {
          providers: [],
        },
        async getRedirectionURL(context) {
          if (context.action === "SUCCESS") {
            return "/brand"
          }
        },
      }),
      SessionReact.init(),
    ],
  }
}

I don't see this cookie. But I'm not logged in and I'm not able to go to /auth

we are using yarn.

yarn upgrade

didn't help

@michaelzhuk can we get on a call to debug please? This seems like tricky one!

also, you must have cookies set against the API domain, otheriwse refresh would not return 200. It would return 401.

And the cookie to check is called

sIRTFrontend

, not

IRTFrontend

(my bad). Can you tell me is

sIRTFrontend

is present or not?

And if there are any browser console logs?

Hello! I would like to implement social login using supertokens flutter sdk, is there any sample code?

We support login for react + NodeJS only. Sample code can be found here: https://supertokens.io/docs/thirdparty/introduction For flutter, we only have session management at the moment.