Hey, after updating to version 7 of supertokens core and version 16 of supertokens-node, I'm facing following error during user signup.

Error: UNKNOWN_USER_ID
    at EmailVerificationClaimClass.fetchValue (/Users/f//backend/node_modules/supertokens-node/lib/build/recipe/emailverification/emailVerificationClaim.js:31:27)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at EmailVerificationClaimClass.build (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/types.js:9:23)
    at Object.createNewSessionInRequest (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/sessionRequestFunctions.js:351:24)
    at Function.createNewSession (/Users/f/backend/node_modules/supertokens-node/lib/build/recipe/session/index.js:48:16)
    at Object.signUpPOST /Users/f/backend/node_modules/supertokens-node/lib/build/recipe/emailpassword/api/implementation.js:561:27)
    at Object.emailPasswordSignUpPOST (/Users/f/backend/apps/supertokens-service/src/supertokens/services/recipes/third-party-email-password.overrides.ts:561:22)...

Not sure it this could be the cause, but at the end of emailPasswordSignUp we call

const response = await originalImplementation.emailPasswordSignUp(
          input,
        );

    /* code for fetching external user */

    await createUserIdMapping({
          superTokensUserId: response.user.id,
          externalUserId: external.user.id,
        });

    response.user.id = external.user.id;
    return response;

We are using: image: registry.supertokens.io/supertokens/supertokens-postgresql:7.0

I am trying to implement websockets in fastapi. I am sendihng the jwt token correctly. And also able to parse it using parse_jwt_without_signature_verification. The payload contains the session Handle. I could not fidn a way to get the session and the user form that. Any help would be appreicated.

Hi, I am associating the roles to a user after the session has already been created, I am trying to manually add the roles and permissions to a session using in the following way in consume override function: def override_passwordless_apis(original_implementation: APIInterface): original_consume_code_post = original_implementation.consume_code_post async def consume_code_post(pre_auth_session_id: str, user_input_code: Union[str, None], device_id: Union[str, None], link_code: Union[str, None], api_options: APIOptions, user_context: Dict[str, Any]): res = await add_role_to_user("public",userid_field, role_name) await session.fetch_and_set_claim(UserRoleClaim) How to get session object inside this signup overide function

Hi, guys! I am having issues with nest js and supertokens integration. When I am trying to signup using url

/api/auth/signup

- I receive error:

{
    "statusCode": 500,
    "message": "Internal server error"
}

And in the logs:

[Nest] 37381  - 09/28/2023, 10:52:11 AM   ERROR [ExceptionsHandler] SuperTokens core threw an error for a POST request to path: '/auth/recipe/signup' with status code: 400 and message: AppId or tenantId not found => Tenant with the following connectionURIDomain, appId and tenantId combination not found: (st-dev-81659d60-5729-11ee-8ee2-61be51f08b14.aws.supertokens.io, public, auth)

Does anyone know what is the issue. Btw I double checked the setup, everything seems like okay... Also, I don't need multitenant login, it's single.

Hi, I have just started to try Supertokens for a Django app with Angular frontend. The sign in works. I have the righr cors policy. I created a new POST api view and tested it with curl to work. However when I call the same endpoint with Angular, I get 403 Error. I have check AuthorisedHosts, CORS headers, CORS policy etc. but to no success. What I may be missing?

Hi, I am trying to trouleshoot why one user is not receiving passwordless login emails, while others do not seem to be experiencing the issue. I've ran a message trace in Exchange and don't see the email ever hitting exchange for this user. I'm using the default email delivery service behavior. Is there some way to see the logs for this?

Are there any foreseeable issues load balancing between 3 exact replicates of an application? 3 Frontends 3 API's, 3 SuperTokens Auth servers, 1 database.

What's the best way to debug why a user can't log in after getting the SMS code with passwordless? (Once they enter the code, it says "Error" even though they are a user)

Hi all, I've noticed that the response times for our python server endpoints using supertokens sessions were longer than expected. So I timed each part of our verify middleware and saw that

verify_session()

was taking around 200~300ms, taking up a majority of the response time. Is this normal? How long is

verify_session()

usually expected to take? I would like to know if there are ways to get this time way down. Here's the snippet:

start = time.time() * 1000
session_recipe = SessionRecipe.get_instance()
supertokens_session = await session_recipe.verify_session(
    request=base_req,
    anti_csrf_check=True,
    session_required=True,
    check_database=False,
    override_global_claim_validators=None,
    user_context=None,
)
end = time.time() * 1000

ThirdPartyEmailPassword: > Removed signInUp and added manuallyCreateOrUpdateUser instead in the recipe exposed functions. > Updated signInUp recipe interface function in thirdparty with new parameters ^Was that intentional? Seems a little confusing. Is the second

signInUp

supposed to be

manuallyCreateOrUpdateUser

?