I want to use supertokens with AWS API gateway+lambda functions I tried following the recipe https://supertokens.com/docs/emailpassword/serverless/with-aws-lambda/backend-config for the backend config, the tutorial says " Create a config.js file in the root directory of your project. " All I have are bunch of lambda functions called from API gateway. Where do I create these files? 🤔

Hi, is there any example of how can I use Facebook provider in react native ?

TRY_REFRESH_TOKEN error

Using emailPasswordSignUp function returns 500 Internal server error

Hello! I am trying to implement OTP in my Android app but the SuperTokens object isn't saving the session information. I am wondering if I initialized SuperTokens incorrectly (or something else) SuperTokens.Builder(applicationContext, apiDomain) .apiBasePath("/api/auth") .build() I can hit apiDomain on my local machine so we can assume this is correct I can see all the session data that I want in the response in logcat but I somehow can't access it in the SuperTokens object

Hi, I'm facing a problem with the

st-auth-mode

request header. First, I do a signup request (using the email password recipe) where I set the header

st-auth-mode: cookie

. I then get a response with

Set-Cookie

headers for the access token and refresh token. This is as expected. Next, I do a signup request where I don't set the

st-auth-mode

header. I then get a response with both

Set-Cookie

headers and

st-access-token

and

st-refresh-token

headers. I do not expect to get the

Set-Cookie

headers. I do a signup request one more time, again without setting the

st-auth-mode

header. This time only the

st-access-token

and

st-refresh-token

headers are set. This is as expected. All signup requests I do afterwards without the

st-access-token

header give the same proper result. The second request should not have returned the

Set-Cookie

headers. Is this a known issue or am I doing something wrong?

Hi please here me here how to setup the supertokens. I am using nest I have 2 microservice: M1 and M2 as API gateway. I have setup the supertokens in M1. it takes cred from M2 and signIn. and return Jwt tokens. In M2(no st) when i verify this token in M2 it gives : { "message": "Invalid token", "error": "Unauthorized", "statusCode": 401 }

I am just starting to work with supertokens. I prepared the project as in the tutorial for AWS lambda. I stopped at the 404 problem and prepared the frontend on this init: appInfo: { appName: "SuperTokens Demo App", apiDomain: "https://api.example.com", apiBasePath: "/auth", apiGatewayPath: "/", websiteDomain: "https://frontend.example.com", }, I prebuild UI and i works. When I try type email to sign up I see network issue: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: GET Status Code: 404 Not Found But when I opened this page I see response: {"status":"OK","exists":false} CORS works: Request URL: https://api.example.com/auth/signup/email/exists?email=asda%40dsa.com Request Method: OPTIONS Status Code: 200 OK I use the API GW V2 with integration for route: ANY /auth/{PROXY+}

I have a question regarding the Apple login process. It seems that sometimes the app doesn't prompt me to share my email address. Most of the time, it doesn't ask, but occasionally, it does. What determines this behavior, and how can we control it? Thank you for your assistance.

How can I get the user email from its session on a backend? E.g. the email that the user used for either passwordless, login/password or social login.