Hey 👋 I'm trying to authenticate via Google using the ThirdParty recipe. We're using NextJS only for the frontend, NestJS for the API, and self-hosted SuperTokens core. The

authorisationUrlGET

request runs successfully but the

signInUpPOST

request receives a 500 in the frontend, and a 401 in the backend. The backend error message is just "Request failed with status code 401". We've successfully used the passwordless recipe with this setup so unsure why Google OAuth is not working. Any ideas?

Did anyone set up Nuxt 3 + Supertokens? Any thoughts how to stay on SSR? Saw only NextJS in guides

Hi, does supertokens support mechanism for device recognition? example use case: detect when an user login happens from a different device. If it does, can you please point me to documentation about it?

Hey, I found a bug in the fetch interceptor in supertokens-website (lib/ts/recipeImplementation.ts) 172:91 When we make our fetch calls we pass a URL object into it as the typescript definitions suggests. Doing that we get the following error:

js
TypeError: url.clone is not a function

and that makes sense as you do the following

js
typeof url === "string" ? url : (url as Request).clone()

the

URL

object does not have the clone methed defined. We currently solve it be calling toString before passing it to fetch, but breaking the fetch api might make other thirdparty dependencies break. You can try it yourself by doing something like this:

js
fetch(new URL(("https://localhost:3000/index.html"))).then(() => {console.log("fetched")}).catch(err => console.log("err", err))

I am developing at sveltekit/capacitor app... in android everything works ok with regrds to supertokens authentication... but in ios devices, I get a successfull sign-in with a success response from server, but then the once I try to authenticate using the

Session

I get:

No session exists

error. Any ideas?

I get error - Please call the supertokens.init function before using SuperTokens even if I call this function with all required arguments. Does anybody have idea why this would happen?

The third party provider google seems to be missing from the backend configs. I am getting this error message while using google third party login What could be the issue? @rp_st please guide

Hi! One question please: what would be the best implementation for a user with "teacher" role, that wants to create emailpassword users with the role "student" in a customize signup page?

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+}