Hi guys! I've come across a pretty strange behavior. I'm using the SDK in a react native app. In order to maintain the session state i routinely check "SuperTokens.doesSessionExist()" and with that answer go forward with an authorized/unauthorized user. What i have discovered is that when the session expires, the method "doesSessionExist", still resolves true.

I'm using the nextjs started integration and when I have an active user session and I hit the /auth route I get caught in an endless redirect loop. Everything's been followed exactly as the integration says

Hi, I followed the nestjs setup guide and when I went to auth/dashboard it showed a server error. Nest app shows this error: SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 401 and message: Invalid API key. The connection uri and api key in nest are the ones provided in the managed service, I don't know what could be wrong.

Hello, wanted to say that I'm struggling a little running the user roles recipe on Safari (works on Chrome) due to line 47 of logger.js: "return errorStack[i].match(/(?<=\().+?(?=\))/g);". This kind of regular expression is not supported in Safari and gives a "SyntaxError: Invalid regular expression: invalid group specifier name". Are there any fixes for this so that I could run my webite on Safari? Edit: logger.js is at supertokens-node/lib/build/logger.js

Hello, i'm having an issue with the integration to NestJs. I'm getting a blank (white) screen when i try to load the dashboard... Everything seems to work fine when i call the signup api from postman though... Any ideas please?...

Hi, I would like to use nock to mock the API call behaind

thirdPartySignInUpPOST

because of some account linking logic we do after it that I would like to test. can you help me understand how the request path looks like and what should be an example of the response? I'm going to use nock to do that if it makes any difference for you

Hey @rp_st for older version of supertoken node - 12.x.x , do we have multitenancy as the recipe ? const Multitenancy = require("supertokens-node/recipe/multitenancy"); I couldn't find this file. Its throwing an error.

hey guys, I hope you're doing well. I'm reaching out because I've encountered an issue with my Django application that involves the @verify_session() decorator provided by SuperTokens. Here's a snippet of my code:

ThirdPartyEmailPassword: > Removed signInUp and added manuallyCreateOrUpdateUser instead in the recipe exposed functions. > Updated signInUp recipe interface function in thirdparty with new parameters ^Was that intentional? Seems a little confusing. Is the second

signInUp

supposed to be

manuallyCreateOrUpdateUser

?

Hello. I've been using the ThirdPartyEmailPassword recipe for my Supertokens setup on the backend and everything worked great. Now I actually wanted to switch to ThirdParty recipe, since I'm not really doing email password login currently in my app. But after switching the backend config to use ThirdParty recipe, the

/{apiBasePath}/signinup

route is no longer there and I can not POST to it. Can anyone suggest what could be the cause? Thanks.