Hi guys! I've come across a pretty strange behavior. I'm using the SDK in a react native app. In order to maintain the session state i routinely check "SuperTokens.doesSessionExist()" and with that answer go forward with an authorized/unauthorized user. What i have discovered is that when the session expires, the method "doesSessionExist", still resolves true.

Is the email template tied to the SMTPService class? I want to enqueue the email to an HTTP endpoint (also easier to integration test) instead of directly connecting to SMTP

For passwordless recipe implementation using web-js-sdk It's not clear from the docs which fn should I use. There are multiple fn is SDK reference. So I'm just guessing from the fn names that probably these are all the steps/code I need to have for authentication 1. Create passwordless code -

superTokensPasswordless.createCode({ email: "john@example.org" })

2. Now either they will type in the code in a form I provide or they will visit the email link. If they visit the link, I will get their code like this

const userInputCode = superTokensPasswordless.getLinkCodeFromURL()

3. Then I will verify the code -

superTokensPasswordless.consumeCode({ userInputCode: "8465AWETA" }).then((res) => { if(res.createdUser){ console.log(JSON.stringify(res.user))} })

Session should be automatically set now Am I missing anything?

Hey guys, what is the reason that Apple has a redirect to

/api/auth/callback/apple

and the others to

/auth/callback/google

for example? (notice the

/api

)

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

How about storing user tokens in a redis cache db?

Hey I'm getting a really weird error where trying to sign in with Google results in this:

Hello! I'm wondering what the timeline is for the 2FA improvements that are listed on the product roadmap? I just started looking at 2FA and the docs have this big Caution banner: https://supertokens.com/docs/mfa/backend/second-factor

Hi there, I am trying to call the sign_up function from the supertokens_python.recipe.emailpassword.asyncio library. When I call

result = await sign_up(sign_up_input.email, sign_up_input.password)

I get the error message

TypeError: sign_up() missing 1 required positional argument: 'tenant_id'

But when I do the call

result = await sign_up(tenant_id="", email=sign_up_input.email, password=sign_up_input.password)

I get the error

TypeError: sign_up() takes 3 positional arguments but 4 were given

Is this a bug? Using version 0.16.0 of the supertokens python sdk

Hello support. I'm tryng to setup the front end sdk for react native on a expo project with react native web. When i try to use the init function. it says that the domain name is invalid but am pretty sure it is and have tested with postman. is there something that im missing or it could be something about the expo and react native web itself that are not compatible. I also tried the web version on it and it seem like it worked. but i dont know if that will be able to work on the andoid and ios side of the app. Ty for you help and if there anything else you need im glad to provide it