Hello, I receive the following error in the browser (MS Edge on Windows 11):

Uncaught DOMException: Failed to execute 'atob' on 'Window': The string to be decoded is not correctly encoded.

The above error occurred in the <SessionAuth> component

. Has this happened to anyone before? I just created two projects with

npx create-supertokens-app@latest

, the first one React+NestJS and the other Vue+NestJS, always the same error

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! why sometimes SuperTokens prints

Failed to fetch

?

Hello, I am using the passwordless recipe for only otp based authentication. Wanted to try the resend code route (signinup/code/resend) feature. Getting this response : { "status": "GENERAL_ERROR", "message": "Failed to generate a one time code. Please try again" } Tried debugging the backend SDK following are the logs for the same: API Server listening on port 3030 com.supertokens {t: "2022-08-02T12:59:42.364Z", message: "middleware: Started", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:158:26" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.364Z", message: "middleware: requestRID is: passwordless", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:172:26" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.365Z", message: "middleware: Checking recipe ID for match: passwordless", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:181:34" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.365Z", message: "middleware: Matched with recipe ID: passwordless", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:194:30" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.365Z", message: "middleware: Request being handled by recipe. ID is: /signinup/code/resend", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:206:30" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.472Z", message: "Sending response to client with status code: 200", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/utils.js:90:14" sdkVer: "11.0.1"} +0ms com.supertokens {t: "2022-08-02T12:59:42.475Z", message: "middleware: Ended", file: "/Documents/supertokens/node_modules/supertokens-node/lib/build/supertokens.js:215:30" sdkVer: "11.0.1"} +0ms Any guidance on how to debug this issue would be appreciated. Thanks .

hi! it's me again 😅 i set up language translations with

next-i18next

library via

translationFunc

like in your guides can i make arbitrary strings from custom additional fields in register page (like labels/placeholders - firstname, lastname) go through this

translateFunc

also?

Hey, when setting custom claims in the access token where is the best place to do that? Using refreshPOST override, or make it a side effect in an api call which is called by the frontend as part of the login process? I've been reading through the docs and I can see a few examples of doing it for a /login route but just struggling to understand is that overriding a login route provided ootb by supertokens or is it in addition to the normal flows?

What's the best way to get the user email here?

consumeCode: async function (input) {
              let { deviceId, preAuthSessionId, userInputCode } = input;
              
              let user = getUserSomehow(deviceId, preAuthSessionId, or userInputCode);

              console.log(user);

              /*if (email) {
                await preventUserSignUpIfTheyAlreadyExist(email);
              }*/

              return originalImplementation.consumeCode(input);
            }

Do I need to put it in userContext? If so, where do I do that?

hey guys, we are a little lost implementing auth for our capacitor apps (different domains)... What's the usecase for the cookieHandler?

js
  supertokens.init({
    ...frontendConfig().appInfo,
    cookieHandler: capacitorCookieHandler,
  })

We are following this guide now, since our implementation didn't work as expected (due to lax cookies & safari webkit issue): https://supertokens.com/docs/thirdpartyemailpassword/advanced-customizations/examples/localstorage/about

Does supertokens use openapi ? if yes, Elixir SDK can be generated via cli. Please let me know.

Hi! What's the recommended way to migrate users to Supertokens? They're just in a DB table, not another identity service. Should I just insert them into the [recipe]_users table? And metadata into the metadata table