Hi @rp_st Looks like the front end module of supertokens tries to call the core in a loop, it's making many calls per seconds without an end.

We are using ThirdPartyEmailPassword and Email Verification recipes together. We need Email Verification only for Email Password users and not for social users. But When we Try to use "@verifySession" annotation in the backend in case of social login. It is considering it as invalid session. and giving an error like this : { "message": "invalid claim", "claimValidationErrors": [ { "id": "st-ev", "reason": { "message": "wrong value", "expectedValue": true, "actualValue": false } } ] } Can anyone please let us know what to do in this case?

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.

What's the best way to manage users (updating user information, resetting passwords) when there are many users? The dashboard doesn't appear to support search and we can't page through 1000s of users…

im trying to get the logged in users email on the backend: const ThirdParty = require("supertokens-node/recipe/thirdparty"); async function generateNewInvoice(req, res, next) { const userId = session.userId; let userInfo = await ThirdParty.getUserById(userId); But it dies at the ThirdParty.getByUserId() method: Uncaught Error Error: Initialisation not done. Did you forget to call the SuperTokens.init function. Im following this guide basically exactly. What am I doing wrong? https://supertokens.com/docs/thirdparty/common-customizations/get-user-info#using-getuserbyid

Hi, I'm trying to implement supertokens with out ldap and AD servers. From my understanding I need to implement a custom provider. I'm just not sure from the example code given how that works? How do we get the client id and client secret?

Hi guys, any idea why when i'm hosting the core myself, even tho my connection string to pgsql is correct it uses in-memory db ? Is there a way to get more logs when starting up ? I only get :

Loading supertokens config.
Completed config.yaml loading.
Loading storage layer.
Using in memory storage.
Loading supertokens version.yaml file.
Started SuperTokens on localhost:3567 with PID: 15384

Anywhere that I could find a example of using Vanilla JS to create custom UI?

What could be causing the login to post to "http://localhost:3000/api/auth/authorisationurl?thirdPartyId=undefined&redirectURIOnProviderDashboard=undefined " when clicking on login with google/github? Nothing has changed with the code for a long time but it has decided to stop working

hi, i faced an issue.

Error: SuperTokens core threw an error for a POST request to path: '/recipe/accountlinking/user/primary' with status code: 402 and message: Account linking feature is not enabled for this app. Please contact support to enable it.