where are you adding the console.log statement?

async function handleSubmit(values) { try { await signUp({ variables: { email: values.email, password: values.password, familyName: values.lastName, givenName: values.firstName, }, refetchQueries: [{ query: UserDocument }], }) router.back() } catch (err) { console.log('err', err) } }

The above is a 200 response error cause the UI should update on its own to reflect that error to the end user

i think its because the res status code is 200

Are you not using our frontend SDK to display the login UI?

no

I see... you should consider using it. Otherwise, you will have to:

async function handleSubmit(values) {
    try {
      let response = await signUp({
        variables: {
          email: values.email,
          password: values.password,
          familyName: values.lastName,
          givenName: values.firstName,
        },
        refetchQueries: [{ query: UserDocument }],
      })
      if (response.status === "FIELD_ERROR") {
        // handle error here..
      }
      router.back()
    } catch (err) {
      console.log('err', err)
    }
  }

are you using react js on the frontend?

yes

then I would really recommend that you use our frontend SDK

and you can customise the UI however you want as well..

how can i add callback that run after signup?

On the frontend: https://supertokens.io/docs/emailpassword/common-customizations/signup-form/handling-signup-success#store-analytics-events

On the backend: https://supertokens.io/docs/emailpassword/common-customizations/signup-form/adding-fields#handle-form-fields-on-successful-sign-up

Would the above callbacks serve your purpose?

yes, thank! i'll try it

a quick fix

return async (root, args, ctx, info, next) => { try { const value = await next(root, args, ctx, info) return value } catch (err) { if (SuperTokensError.isErrorFromSuperTokens(err)) { throw err } } }

Did the above fix your issues?

Yes

I replace error handler middleware

So wait, the errors thrown by supertokens are not getting handled anymore? Cause some of them are important to be handled by supertokens itself.

otherwise other things will break.

where is the best place in the source to find the default values for this config object on the Session recipe? https://supertokens.io/docs/nodejs/session/init

Default values: - cookieSecure: (if your API domain has https, then this is true, else false) - cookieSameSite: (If your API domain and website domain share the same top level domain, this is

lax

, else it's

none

) - sessionExpiredStatusCode: 401 - cookieDomain: (This is the hostame of the api domain you provide) - sessionRefreshFeature -> disableDefaultImplementation:

false

- errorHandlers -> our own error handlers - enableAntiCsrf: If the same site is

lax

, this is

false

, else it is true.

also, what is the actual default refresh api?

sessionRefreshFeature
disableDefaultImplementation
type: boolean
description: Disables the default refresh API

this might be a silly question but for the for the apiDomain and the websiteDomain i'm assuming that when we deploy, these are the public urls correct? currently our api domain would be: https://api..com our website domain would be: https://www..com

yea.. correct

for development i have them both pointing to localhost, but they are using different ports