import { addAxiosInterceptors } from "supertokens-web-js/recipe/session". This function is depricated. I use axios with create and interceptors. What can I do?

Hi @everyone, I am Zohra and wanna contribute to SuperTokens I am trying to run the Supertokens-core manually After this command

./startTestEnv —wait or ./startTestingEnv —wait


 I am getting this error

*Could not compile settings file '/Users/zohra/OpenSource/supertokens/supertokens-root/settings.gradle'.
> startup failed:
  General error during conversion: Unsupported class file major version 61
  
  java.lang.IllegalArgumentException: Unsupported class file major version 61
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:189)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:170)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:156)
        at groovyjarjarasm.asm.ClassReader.<init>(ClassReader.java:277)
        at org.codehaus.groovy.ast.decompiled.AsmDecompiler.parseClass(AsmDecompiler.java:81)
        at org.codehaus.groovy.control.ClassNodeResolver.findDecompiled(ClassNodeResolver.java:251)
        at org.codehaus.groovy.control.ClassNodeResolver.tryAsLoaderClassOrScript(ClassNodeResolver.java:189)
*

Any help is appreciated Thanks

Hey @rp_st we want to authenticate whether the client redirect URL is correct or not, if it is correct, then only we want to generate the accesstoken 1.can you show us is it possible or not? if yes, how? 2. does the supertoken store the client redirect url or not in their system? and if they do, what is the method from nodejs-sdk to verify the client redirect url?

When self-hosting, is there a good reason why not to run the core on the same server as the backend? I'm using a DigitalOcean droplet which will run my app backend, supertokens backend and I'm thinking why not run the core there too?

hello, I had some question regarding session sharing across subdomains. At the moment im deploying on running on localhost. I have the main domain localhost:3000/ and a subdomain blog.localhost:3000/. The problem im coming across is that when i access the subdomain it redircts me to the login page to login and even if i do login it redirects me back to the login page. The session returns unauthorized. I looked into session sharing and the sessionTokenFrontendDomain i set to ".localhost" but in the caution section of the documentation it says I should not set it to localhost. I instead have indeed declared on my /etc/hosts file the subdomain for blog.localhost. However the problem persists. Am i missing a step? Also do i keep the sessionTokenFrontendDomain with the mention in the hosts file or i remove it?

Hi. In my nestjs app, i have implemented the auth guard. After a successfull login, at the next reuqest, my

response.headersSent

is true and the user get redirected to login. So I guess that the verifySession is failed but i dont have info why it was failed even though the original login was successfull. the err is not set:

await verifySession()(request, response, (res) => {
      err = res;
    });

how can I debug and understand why am i getting redirected to login page? Thanks

Hello, I'm trying to use supertokens selfhosted with multitenancy and dahsboard and I have 2 issues that appeared this week. 1. When accessing the dashbord there is no "add user" button. 2. When trying to use multitenantcy I get an error saying that the feature is not configured or I need a licence. Both of these issues were not happening last week. I was using supertokens core 7 and after noticing the issues I upgraded to version 9 both with postgres.

Hello, I am having issue with API /signinup, it is being called twice, already looked at other discussions in here but I still don't know how to prevent I am using SuperTokens Core (Managed) v7.0, front-end I am using React with "supertokens-auth-react": "0.31.5", back-end is ExpressJS with "supertokens-node": "13.6.0"

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?...

Hello 👋 I want to add metadata to my existing users. However, all of the python examples I can see are about running init() and sdk functions from within flask/fastAPI/django. Is there a way for me to use supertokens sdk on a standalone python script, point it to the supertokens instance I have on my backend (postgres), and add the metadata? My hacky solution is to directly update the

user_metadata

table on postgres, but that's a rast resort