Oh wow.. okay. Can you please open a GitHub issue about this?

I have just created it, it's available here: https://github.com/supertokens/supertokens-auth-react/issues/364

Thank you. We will have a look

Hey there, I’m setting up email verification, and am a bit stuck. Log in and Sign up, works. But email verification does not send an email. Is there anything I need to set up on the backend? The error logged in the console and network tab (screenshots attached) My front-end:

SuperTokens.init({
  appInfo: {
    appName: 'app',
    apiDomain: webAndApiDomain,
    websiteDomain: webAndApiDomain,
  },
  recipeList: [
    EmailPassword.init({
      emailVerificationFeature: {
        mode: 'REQUIRED',
      },
      palette: {
        primary: colors.turquoise,
      },
    }),
    Session.init(),
  ],
});

Back-end:

supertokens.init({
  framework: 'fastify',
  supertokens: {
    connectionURI: process.env.SUPER_TOKENS_CONNECTION_URI,
    apiKey: process.env.SUPER_TOKENS_API_KEY,
  },
  appInfo: {
    appName: 'app',
    apiDomain: webAndApiDomain,
    websiteDomain: webAndApiDomain,
  },
  recipeList: [
    EmailPassword.init(), // initializes signin / sign up features
    Session.init(), // initializes session features
  ],
});

Hey @Quinnfinite seems like a bug on our end for json parsing in the API. Will fix it today. In the meantime, can you please open an issue about this on our GitHub?

@User I am in the middle of fixing this issue from our frontend SDK. Should be released in a about 1 to 2 hours.

@User Thank you! Just opened an issue with some extra information on what I found as I was digging around https://github.com/supertokens/supertokens-node/issues/247

thanks!

@User released a new version of supertokens-auth-react with the fix.

Please feel free to reopen the issue in case the error still persists.

Hey, (First of all: I hope this is the correct channel for the following) 😇 I'm currently working on a new webpage and looking for an easy although secure way to handle sessions. Login is no issue at all, because I'm using OpenID Connect. So theoretically I only need the bare minimum session management, which would be: - creating sessions - verifying sessions - revoking session I found supertokens yesterday and was very impressed with the project. There is one small issue tho: I'm using rust for my backend and as far as I can tell there is no official or unofficial supertokens SDK. So I browsed through the docs, looking which endpoints I would have to implement for my limited use-case. As far as I can tell I only need to implement

/signout

and

/session/refresh

(according to this: https://app.swaggerhub.com/apis/supertokens/FDI/1.12.0#/) Am I missing something? I couldn't find proper docs on what exactly, each endpoint needs to do. I looked through some implementations and I have to say that most of them are not as straight-forward as I hoped and quite complex to understand (obviously, because they have to handle much more use-cases and options then I would need) Is there proper documentation on implementing a SDK for a new language, or do I just have to go though existing implementations? Thanks a lot in advance 🤗

Hey @DerZade you would need to implement those two APIs. But you would also need to implement functions for createNewSession. The main complexity lies in setting cookies and headers + verifying the session within the rust layer itself for efficiency.

If you’d like, we can arrange a call so that I can take you through the node SDK implementation which can be ported to rust

Thats what I thought 😄

Yeah why not I'll shoot you a PM

Cool!

Hi guys. Every time I sign in(using either ReactJS implementation or nextJS implementation), it takes 4 to 5 seconds to signin and 2 to 3 seconds to sign out. In dev tools > network, it seems it spends a few seconds executing "recipeImplementation.js". Has anyone been able to cut down on this? Thanks

hey @User are the API calls taking that long? Or something else?

yes, it seems API calls are taking 4 to 5 seconds. Initially I thought my implementation. But I tried this repo: https://github.com/supertokens/next.js/tree/canary/examples/with-supertokens and also the ReactJS implementation. they both took similar time.

So it seems to be the problem of cold start in serverless functions. Normally this is solved by keeping the serverless functions warm by sending a periodic ping to them.

Also, are you using try.supertokens.io as the connection URI? That instance is located in India region and if you are not close to that, that may add further delays

so, would it be better to have a self hosted implementation to improve the latency?

Yea. for sure. Or you could sign up and use our managed service to deploy the core in a location closer to where the lambda functions run.

ok got it. Thanks for the response @User . Else I would have been running in circles.

Happy to help 🙂

Hey all, I am setting up Supertokens with Next.Js project and Flask. So my backend APIs' are running on Python flask on Http://localhost:5000/ and Next.js App is running on http://localhost:3000/. Using Managed service as Core. Followed Next.Js steps and can see the login page but when trying to signup or login I am getting CORS errors. Questions: Do I need any changes to Flask to make backend work or not? How to fix CORS errors? Please advise. Thanks in Advance.

NextJs_Flask Setup Questions

Hi everyone. 👋 I hosted my supertokens core behind a reverse proxy at example.com/supertokens. I'm using

connectionURI: 'https://example.com/supertokens/'

, but it seems like my backend is trying to make requests like

https://example.com/apiversion

. Does supoertokens support using a base path/prefix for the connectionURI? Seems like it is ignored.

@User we don't support base path for the connection URI :(. You will have to give a sub domain for the core. If you'd like this feature, please feel free to open an issue about this on our github.

Is there any examples of using supertokens with a custom UI for us non-react users? I'm having a hard time with that.