hi! how can i prevent

SignInUp

component from

supertokens-auth-react/recipe/passwordless

redirecting to

/auth

i am overriding it to only confirm

OTP

by creating

verify-phone

route, and adding this to frontend config

signInUpFeature: { disableDefaultUI: true }

Hey I have a issue with my capacitor ios app again. Here is the debug log from the phone. It logs in normally and cannot hold session somehow. Any ideas?

This may be a bit of a basic question, but in some cases the supertokens instance is not found even though I initialize Supertokens as the first thing in the app. Now I am trying to get the user count in a request handler, and it is saying that Supertokens is not initialized :/

await supertokens.getUserCount()

Hello This seems like an awesome project. I currently have my users in my mongoDB and logins in google identity management. In the future it would be cool to have everything in mongodb (when the adapter is implemented). My backend is built with c# in asp core. I dont see any mentions of dot net / asp core / c# in the guides or in this discord. Will it be supported or am i the only one who have requested it ?

My session keeps expiring I tried adding the frontend SDK to all of my pages but it doesn't seem to work

i want to use supertokens_python with websockets in fastapi. is there a verify_session that works for a websocket route?

Bom dia (Good Morning) I am implementing super tokens on django (backend), using thirdparty (only) recipe. I would like your opinions for best practices on how to initialize it. Currently I have a module and using the module config, I'm calling the start method where I have the init function. (I'll attach some screenshots) Still says that it is not initialized

https://discord.com/channels/603466164219281420/907932061669654548/1202007865028775937 I've started the migration from the Remix example to the Next.js app directory example. (At least for now.) And I think Remix does things way better. 😅 I wanted to suggest adding documentation on how to use the

ThirdPartyEmailPassword

option without using the Express middleware, and perhaps suggest exposing clear functions for it if they aren't yet available. (I assumed that they would be available since we now have things like

*withoutRequestResponse()

.) I've been approached multiple times on both my Remix and my SvelteKit examples regarding how to get

ThirdPartyEmailPassword

up and running. It seems to be the most common recipe (or one of the most common). And having a way to set things up clearly (without having to bring other SuperTokens packages into the mix) would likely be a big win. It might also alleviate some of the package management that SuperTokens has to deal with for various JS frameworks. I would look into it, but I unfortunately haven't had the time to scrutinize SuperTokens's internals like I did last time. 😅 I'm still looking for an opportunity. I'm only just now getting to the Next.js app dir example. (I know SuperTokens has one. This would just be one that would be more direct -- requiring less NPM packages and higher order functions.)

We are trying to host our system on GCP. We are using email password recipe and we want to use cloudrun. Just need some pointers on resources that will help to do this or if it is even possible. Thanks!

Good morning. Is there anyway to get the user password hashes from ST's API?