I am testing a service using a hosted production supertokens using a valid sms key, and I need to perform OTP sign in many times. However all of a sudden I stopped receiving sms messages and there are no logs in the console. I am wondering if this could be due to some default spam detection or if this could be due to some rate limiting against my phone number?

Hi Supertokens Team, I hope this message finds you well. I am currently working on integrating Supertokens into my application, which consists of Vue.js on the frontend and Nest.js on the backend. Initially, I successfully implemented the Supertokens login functionality using the SaaS version, and everything worked smoothly. To facilitate local development, I decided to switch to the Docker version of Supertokens by setting up a local instance and updating the connectionUrl accordingly. After successfully completing the setup, including table creation, both the Supertokens core and database containers appear to be running correctly on my local environment. However, upon switching the backend's connectionUri to the local URL, I encountered an issue. The login form displays as expected, and I can successfully log in with Google authentication. However, instead of being redirected to the application's homepage, the Supertokens session refresh logs continuously appear, causing an infinite loop. When I revert the connectionUri to the SaaS version, everything functions correctly. I've attached a portion of the logs generated endlessly on the frontend for your reference. Could you please provide guidance on what might be causing this issue? Any insights or suggestions would be greatly appreciated.

Hi, is the types for the default translations from the recipes in supertokens-auth-react exported?

Is it possible to modify the "Sign In" text in the prebuilt UI such as adding additional text?

Hi 🙂 After reading the docs, I'm unsure what to do in my use case. I have a social login set up in nextjs, and I would like to send the provider refresh token to my backend API (different service). I already extracted the refresh token in the backend config

override.functions.signInUp

section. I need to make an authenticated call to my backend with the current user. Since I don't have a session in the

override.functions.signInUp

function, I'm unsure how to proceed. Will appreciate your help 🙏

Hi, I'm trying to setup the dashboard. I'm trying to create a user using the CLI command but I'm getting

{"status":"INVALID_EMAIL_ERROR"}

curl --location --request POST 'https://xxx.aws.supertokens.io/recipe/dashboard/user' \
--header 'rid: dashboard' \
--header 'api-key: <YOUR-API-KEY>' \
--header 'Content-Type: application/json' \
--data-raw '{"email": "<YOUR_EMAIL>","password": "<YOUR_PASSWORD>"}'

My email ends in

.dev

is there some validation going on?

Any ETA on bun runtime based sdks for auth? Apparently using supertokens/node shoots random error on Elysia framework

@rp_st There is a problem with the frontend. If I clear the st-last-access-token-update cookie and then try to login/signup, supertokens' backend will start giving error. Even after reloading the page, it won't work. It happened with me earlier also but that was because I was using * in cors , but now that is not the case. My backend supertokens-python version is 0.12.6, in the frontend the versions are: "supertokens-auth-react": "^0.31.1", "supertokens-node": "^13.0.2", "supertokens-web-js": "^0.5.0",

Any ideas why my supertokens when deployed doesn't return any cookies but still return 201. But running the same locally I get 201 and cookies? (using postman to test) ?

Hi, I am trying to implement SSO between two rails websites with different domain names, e.g. a.com and b.com . Is SuperTokens the right tool for me? We want a phone-password login. Do I just use the

with-phone-password

react example code on each site, or do I need another site like c.com to let the user redirect to for authentication? And how do configure to let it know which domains should share the same session? Sorry I'm quite confused.