I am getting a weird issue on refresh. The auto refresh works on get requests but not put/post requests.

Hello, I am trying to deploy host my backend in a k8s cluster and I've got everything up and running except the hosting of the supetokens instance that at the moment throws this error (see picture) "Unknown API called" I've searched without getting any hits att all for this error. Is there something specific I need to think about when hosting my supertokens instance in my k8s kluster? Does anyone know why it's throwing this error and what it means? Thanks in advance for any help!

Any reason why CORS would fail with

Access to fetch at 'http://localhost:3000/v1/auth/signin' from origin 'http://localhost:4200' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

cors:

app.enableCors({
    origin: "http://localhost:4200",
    allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

backend config:

{
  config: {
    appInfo: {
      appName: 'app',
      apiDomain: 'http://localhost:3000',
      websiteDomain: 'http://localhost:4200',
      apiBasePath: '/v1/auth',
      websiteBasePath: '/auth'
    },
    connectionURI: 'http://auth:3567',
    apiKey: 'supersecret'
  }
}

frontend config:

apiBasePath: "/v1/auth"
apiDomain: "http://localhost:3000"
appName: "app"
websiteBasePath: "/auth"
websiteDomain: "http://localhost:4200"

EDIT: using nestjs

Hello, wanted to say that I'm struggling a little running the user roles recipe on Safari (works on Chrome) due to line 47 of logger.js: "return errorStack[i].match(/(?<=\().+?(?=\))/g);". This kind of regular expression is not supported in Safari and gives a "SyntaxError: Invalid regular expression: invalid group specifier name". Are there any fixes for this so that I could run my webite on Safari? Edit: logger.js is at supertokens-node/lib/build/logger.js

TRY_REFRESH_TOKEN error

Using emailPasswordSignUp function returns 500 Internal server error

I get error - Please call the supertokens.init function before using SuperTokens even if I call this function with all required arguments. Does anybody have idea why this would happen?

Hi, I was wondering how to create a custom signin/signup UI for a NextJS integration. I am currently successfully using the pre build UI [1], however I'm not sure how to start creating a custom UI. - Should it be in the same file (

pages/auth/[[...path]].tsx

)? If so, where do I put my components? If not, which file should I use? - The example of the custom email password signin [2] only shows the callback function. Is there an example of building a custom UI in NextJS? - Is there a certain structure to keep in mind such that I can easily later add alternative signin/signup methods? [1]: https://supertokens.com/docs/emailpassword/nextjs/setting-up-frontend [2]: https://supertokens.com/docs/emailpassword/custom-ui/email-password-login

hi, when i create a user , the primary user flag is getting set as false , but i need it to bet set as true by default to enable account linking from different social logins

Once client Application send token (generated by SuperToken) to backend API, how backend API will validate the token