Hi, thank you for an amazing work! I've use the Passwordless recipe with Ionic app and developer/user experience was amazing. Now I'm trying to figure out, if it is possible to use a single API and 2 frontend with different domain names? In my case ionic use localhost in hybrid app, but to publish it on the web I need another registered domain name.

Is multiple emails associated with one account supported?

backend server graphql used, i am using graphql but i think i am going wrong somewhere

Hi 🙂 Can we change the user ID when we create the user manually ? I found Changing user ID format but Docs for this are coming soon And my need is more to set a custom ID already defined when I use

emailpassword.SignUp

Hello. We have been using super tokens for the last few months with no issues. Today we are seeing a lot of session refresh errors frequently. "Error: SuperTokens core threw an error for a POST request to path: '/recipe/session/refresh' with status code: 500 and message: Internal Error\" I've been checking refresh requests in postman and every 3rd odd request fails, then the next succeeds. We are using the latest versions of the node-sdk. Using passwordless with roles on managed ST. Anyone else seeing this or any idea of how to solve this error?

I saw that there is a special case for apple to set redirect url.

Hi there, needing some help with emails! I customised the email template for email verification in node.js and I'm trying to add an extra query string to the emailVerifyLink in my backend config. I need to get the value of this query string from the current url. I see that there is an express request available in the userContext._default object via the emailDelivery.service.override.getContent function input. Is this the best place to get the query string? And if so how would I do it? Thanks!!

I'm bummed out hard on "can't connect to core" stuff and I've seen it throughout this discord channel (probably the thing @piano1029 posted right above me I bet). Everything's running via docker-compose and I know my app can communicate with supertokens because I have the dashboard installed and I can see it making queries here: http://localhost:3999/api/auth/dashboard But, when I try and signup via my FE, I get 404s from my BE. So what's awesome is that I know the requests to my BE work and end up going to supertokens because I get 200s from URLs like: http://localhost:3999/api/auth/dashboard/api/users/count. But I get 404s from URLs like: POST http://localhost:3999/api/auth/signup Why would this happen?

Hey, when I create a role in super tokens managed service. It does not adds that role to the session when I call a url to get user data. I am using req.session!.getClaimValue(UserRoles.UserRoleClaim) to get the user role.

Hi, I'm trying to use the usermetadata recipe on our hosted instance (prod v3.10) I get the following error for an update or a getUserMetadata :

'Error: SuperTokens core threw an error for a GET request to path: '/recipe/user/metadata' with status code: 404 and message: Not found\n\n    at Querier.<anonymous> (/workspaces/poppy/node_modules/.pnpm/supertokens-node@12.1.0/node_modules/supertokens-node/lib/build/querier.js:252:31)\n    at Generator.throw (<anonymous>)\n    at rejected (/workspaces/poppy/node_modules/.pnpm/supertokens-node@12.1.0/node_modules/supertokens-node/lib/build/querier.js:22:44)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)'

I can indeed see a 404 on

https://MY_DOMAIN:3567/recipe/user/metadata

Does my instance need to be updated?