Any idea why setting the

api_domain

on my python backend to be an AWS Public IPv4 DNS address is throwing this error?

Traceback (most recent call last):
  ...
  File "/home/andrew/PycharmProjects/reminderFastApi/venv/lib/python3.10/site-packages/supertokens_python/__init__.py", line 35, in init
    return Supertokens.init(
  File "/home/andrew/PycharmProjects/reminderFastApi/venv/lib/python3.10/site-packages/supertokens_python/supertokens.py", line 209, in init
    Supertokens.__instance = Supertokens(
  File "/home/andrew/PycharmProjects/reminderFastApi/venv/lib/python3.10/site-packages/supertokens_python/supertokens.py", line 157, in __init__
    self.app_info = AppInfo(
  File "/home/andrew/PycharmProjects/reminderFastApi/venv/lib/python3.10/site-packages/supertokens_python/supertokens.py", line 108, in __init__
    self.top_level_api_domain = get_top_level_domain_for_same_site_resolution(
  File "/home/andrew/PycharmProjects/reminderFastApi/venv/lib/python3.10/site-packages/supertokens_python/utils.py", line 279, in get_top_level_domain_for_same_site_resolution
    raise Exception(
Exception: Please make sure that the apiDomain and websiteDomain have correct values

im trying to get the logged in users email on the backend: const ThirdParty = require("supertokens-node/recipe/thirdparty"); async function generateNewInvoice(req, res, next) { const userId = session.userId; let userInfo = await ThirdParty.getUserById(userId); But it dies at the ThirdParty.getByUserId() method: Uncaught Error Error: Initialisation not done. Did you forget to call the SuperTokens.init function. Im following this guide basically exactly. What am I doing wrong? https://supertokens.com/docs/thirdparty/common-customizations/get-user-info#using-getuserbyid

Hey there, back with another few questions. 😇 I am planning the upgrade from

supertokens-core

v3.16.2

to

v4.0.0

and I have a few questions around the database changes for the

emailpassword_users

and

thirdparty_users

table: Why did you choose

VARCHAR(256)

and

VARCHAR(128)

over just

TEXT

? The latter would have required no database migration and would not require a database migration in the future if the value changes again. Is it safe for me to use

TEXT

instead of

VARCHAR(256)

- or does

supertokens-core

do some kind of database schema validation? How did you manage to roll this out in production? In my current understanding it is not possible to apply this migration without locking the full database table and rewriting every single row. Wouldn't it been smarter (and also less "breaking") to follow this strategy: 1. Add a new columns "thirdparty_users"."third_party_user_id_new" and "emailpassword_users"."password_hash_new" 2. Run a script during outside of a migration/lock that copies the values from the old column to the new column 3. Write the super tokens code in a way that it can deal with both the old and new columns for the duration of the copy from old to new column period Right now, for us running the migration will probably not take longer than a few seconds - however, I am concerned that in the future additional breaking database changes will make it harder for us to migrate to the latest versions. Since you probably have much more users running on your hosted solution, I am especially curious on any insights on how you manged this (of course only if it is possible to share that information)!

I have a FastAPI backend and a NextJS frontend. I want to use getServerSideProps to send the logged in user's data to my frontend. When I try to get the logged in user's data in getServerSideProps, I get { message: 'unauthorised' }. I think this is because the cookies in the browser are not sent to my FastAPI backend. Is this even possible?

hello guys, can i change the language in button or header ?

Hi, I'm trying to implement supertokens into my nestjs + nextjs application with ThirdPartyEmailPassword. I encountered an error when trying to signin/signup with Google. The account is successfully signup/signin in the development environment but the /signinup api failed with status code 500 on frontend 400 on backend, then the error got displayed on the form. When reload the frontend application, it does recognize that I've logged in and redirect to the home page tho.

If the supetoken-core is running in docker, How to allow cors origin? I am getting this error - "from origin 'http://localhost:3001' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The value of the 'Access-Control-Allow-Credentials' header in the response is '' which must be 'true' when the request's credentials mode is 'include'."

Hi. for handing errors in typescript, is there any way to not have error in the catch block as an any type?

// eslint-disable-next-line @typescript-eslint/no-explicit-any
} catch (e: any) {
  if (e.isSuperTokensGeneralError) {
    ...

Hello @rp_st I am using python flask backend and on clicking on reset password the api gives 200 respond but I am not able to receive email . AFAIK from the documents even if I don't add any smtp configurations I should still get an email from supertokens domain or I am missing sth here ?

Hi! I'm trying to implement UserRoles in my nextjs app and I'm getting

Initialisation not done. Did you forget to call the UserRoles.init or SuperTokens.init functions?

when I try to create a role. Does anyone have an idea what I could be doing wrong?