NestJs and Vuejs Role route verification implentation from documentation is not working

Hi, I get error 500 when calling

signInAndUp

but after subsequent calls (maybe or two), I will get success. Is this common behavior for third party login?. I just wrapped logic in for loop to fix. But if anyone knows why that would be better

Noob here, the data inside jwt is not encrypted? The st-access-token in postman is showing the data when pasted in jwt.io

Hi, I am a student and I created a mobile app in Flutter, and I came across SuperTokens and want to implement its authentication in my app , I tried searching online for any tutorials or proper documentation but couldn't find any. Can you please suggest a few resources to help me. Thank you

Give more communication and time to pr senders. I wasted 2 weeks in total. (https://github.com/supertokens/supertokens-node/pull/505) You are constantly releasing every new version and I'm tired of constantly equalizing with those versions.

I am running my site on localhost as well as on a webserver. On localhost, the following line works fine, but when deployed on a webserver, it throws a 404 redirectToAuth({ show: "signup" }); When I go to api.mydomain.com/auth/dashboard I am able to login with my API key but then I get this Server Error: Failed to load user list. Please refresh to try again. any ideas / suggestions? Thanks!

Hii, I have integrated super token's passwordless recipe for Python fastAPI and there is a scenario in which I need the user's user_id at a verify code time(before login) Is there any way to get the user_id by access token? Thanks

I'm seeing an issue where an expired role claim is not being refreshed on the frontend:

{reason: {message: 'expired', ageInSeconds: 7358.774, maxAgeInSeconds: 60},validatorId: "st-role"}

. It seems to be what was described in https://community.supertokens.com/t/2912951/hello-im-following-the-new-docs-on-how-to-implement-role-bas , but I'm on a recent version of the SDKs. Is there something else I need to do to cause expired claims to be refreshed?

Hey, I'm getting "u.getSuperTokensRoutesForReactRouterDom is not a function" after upgrading from "supertokens-auth-react": "0.31.1" to latest. Do you have any bug report mechanism?

I'm trying to get a working setup locally where I have two front end applications. One is running on localhost:4200 and the other is running on localhost:8080. The API that is exposing Supertokens is running on localhost:3000. Is there any way with the

websiteDomain

configuration to get this running? It seems that only one front end is able to actually initiate login/logout but both can share the session if the one with the matching website configuration initiates it