603466164219281420 #support-questions

Yeah I have seen that. Actually, I have the setup running with REST. I wanted to move towards graphql. Just wanted to use the prior knowledge if there would be any.

04/06/2021, 1:37 PM

So the auth APIs that are exposed via the node SDK will continue to be REST. So you will only need to figure out session management with graphql. I'd be happy to get on a call to help you figure this out

Sheraz

04/06/2021, 1:41 PM

That would be great. I will request you for that.

04/06/2021, 1:51 PM

Please check your DM @Sheraz

othiagocruz

04/08/2021, 6:18 PM

Copy code

2021-04-08T18:17:04.274Z    45a8a61c-8e0e-47a1-8b49-d6a56b09f0fe    ERROR    SessionError {  getRecipeId: [Function (anonymous)],  type: 'GENERAL_ERROR',  message: 'Initialisation not done. Did you forget to call the SuperTokens.init function?',  payload: Error: Initialisation not done. Did you forget to call the SuperTokens.init function?      at Function.getInstanceOrThrowError (/var/task/node_modules/supertokens-node/lib/build/recipe/session/sessionRecipe.js:307:26)      at getSession (/var/task/node_modules/supertokens-node/lib/build/recipe/session/index.js:26:40)      at handler (/var/task/.next/server/pages/api/me.js:88:86)      at apiResolver (/var/task/node_modules/next/dist/next-server/server/api-utils.js:8:7)      at processTicksAndRejections (internal/process/task_queues.js:93:5)      at async Server.handleApiRequest (/var/task/node_modules/next/dist/next-server/server/next-server.js:67:462)      at async Object.fn (/var/task/node_modules/next/dist/next-server/server/next-server.js:59:492)      at async Router.execute (/var/task/node_modules/next/dist/next-server/server/router.js:25:67)      at async Server.run (/var/task/node_modules/next/dist/next-server/server/next-server.js:69:1042)      at async Server.handleRequest (/var/task/node_modules/next/dist/next-server/server/next-server.js:34:504),  recipe: undefined,  errMagic: 'ndskajfasndlfkj435234krjdsa'}

hey im getting this error when trying to run supertokens on vercel, not sure whats going on, local it works

04/08/2021, 6:19 PM

Are you getting this when an API is called?

othiagocruz

04/08/2021, 6:20 PM

yeah

04/08/2021, 6:20 PM

Ok so in that API, you need to call the supertokens.init function at the top (from supertokens-node)

04/08/2021, 6:21 PM

Just like you call it in _app.js (but only the supertokens-node one)

04/08/2021, 6:21 PM

And you may want to add that init call to all APIs that use supertokens

04/08/2021, 6:22 PM

On local it works cause it’s not truly serverless, so the init call done in _app.js is retained.

04/08/2021, 6:23 PM

(We will update the example repos with this too. Thanks)

othiagocruz

04/08/2021, 6:24 PM

that make sense let me try to init it where im using it

04/08/2021, 6:25 PM

Yea. At the top of that file. Just need to call that once per api route

othiagocruz

04/08/2021, 6:32 PM

worked! 👍🏼

deltasoneca

04/12/2021, 12:37 PM

Hi, my style customization of the Sign Up form is just not working. I am following the documentation, running it locally, and the style is not applied at all. Here is the relevant part of my config file:

Copy code

export let frontendConfig = () => {
  return {
    useReactRouterDom: false,
    appInfo,
    recipeList: [
      ThirdPartyEmailPasswordReact.init({
        signInAndUpFeature: {
          defaultToSignUp: true,
          signUpForm: {
            style: {
              button: {
                backgroundColor: '#252571',
                border: '0px',
                width: '30%',
                margin: '0 auto',
              },
            },

I am using the versions "supertokens-auth-react": "^0.8.0" and "supertokens-node": "^4.2.0". Any ideas why?

04/12/2021, 12:42 PM

hey @User try moving the

style

object outside of

signUpForm

04/12/2021, 12:42 PM

so it should still be inside

signInAndUpFeature

04/12/2021, 12:42 PM

Copy code

export let frontendConfig = () => {
  return {
    useReactRouterDom: false,
    appInfo,
    recipeList: [
      ThirdPartyEmailPasswordReact.init({
        signInAndUpFeature: {
          defaultToSignUp: true,
          style: {
              button: {
                backgroundColor: '#252571',
                border: '0px',
                width: '30%',
                margin: '0 auto',
              },
            },
          signUpForm: {
            ...
          }

deltasoneca

04/12/2021, 12:43 PM

Great, it worked now! Thanks @User (documentation is wrong btw: https://supertokens.io/docs/emailpassword/common-customizations/styling/changing-style)

04/12/2021, 12:43 PM

thanks! we will fix it

04/12/2021, 12:45 PM

Also, you are looking at the emailpassword recipe, whereas you are using thirdpartyemailpassword recipe. (But the same docs for that are wrong still)