Hi, got a little issue with our Android app on react native for a few days. it can log in and get an access token but when refreshing it logs us out this is what we changed before it started to happen : - "supertokens-node": "^8.5.0", + "supertokens-node": "^9.2.3", in the same deployment, we also set the cookieDomain to a wildcard to allow subdomains the weird thing is ios is fine

Has anyone successfully run supertokens core on heroku with heroku's psql? I'm getting an issue with drivers. The database url begins with

postgresql://

so it seems the

jdbc:

prefix is coming from someplace else?

Setting up PostgreSQL connection pool.
2022-10-07T02:04:20.842175+00:00 app[web.1]: Stopping SuperTokens...
2022-10-07T02:04:20.856938+00:00 app[web.1]: What caused the crash: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgres://ec2-107-23-76-12.compute-1.amazonaws.com:5432/....

I am running supertoken using self-hosted core. I want to run both my auth server (nestjs) and auth core using docker-compose. The issue is I am not able to pass the connectionURI of the core to the server. my authcore service is named -

authCore

so I tried passing

authCore:3567

but this doesn't work I see following error -

Error: Please provide a valid domain name
    at normaliseURLDomainOrThrowError (/app/node_modules/supertokens-node/lib/build/normalisedURLDo

    at new NormalisedURLDomain (/app/node_modules/supertokens-node/lib/build/normalisedURLDomain.js

    at /app/node_modules/supertokens-node/lib/build/supertokens.js:350:39
    at Array.map (<anonymous>)
    at new SuperTokens (/app/node_modules/supertokens-node/lib/build/supertokens.js:348:24)
    at Function.init (/app/node_modules/supertokens-node/lib/build/supertokens.js:372:36)
    at new SupertokensService (/app/src/auth/supertokens/supertokens.service.ts:15:17)
    at Injector.instantiateClass (/app/node_modules/@nestjs/core/injector/injector.js:358:19)
    at callback (/app/node_modules/@nestjs/core/injector/injector.js:59:45)
    at Injector.resolveConstructorParams (/app/node_modules/@nestjs/core/injector/injector.js:139:2

Hey there, it seems SuperTokens doesn't have a PHP SDK?

@rp_st Hey guys, Do you have an SDK for Remix?

Hey @rp_st I want to get a list of all the users I have, but I want to do it from a script, not a server. I saw that there is a function in the node-supertoken lib but Im not able to use it (because I cannot use init()). I saw that there might be an endpoint in the CDI, but when I try to use GET im getting 404 not found in response. What is the right solution here? Thank you

Hi, I am stuggling to find how to refresh the session using the header transfer method , by manually doing XHR Requests to the /auth/ endpoints. It seems the that refreshed token is sent using cookies instead of response headers. Currently I am trying with the following POST: What am I doing wrong?

api.post('/auth/session/refresh', 
           null,
           {
             headers: {
               Rid: "session",
               Authorization: "Bearer "+ refreshToken,
               "St-Auth-mode": "header", 
            }
          });

SESSION STILL AVAILABLE AFTER REVOKING IT

I am having a new error now at iOS only, Supertokens throws this "Please provide a valid domain name":

(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$/.test(r))?"http://"+i.host:"https://"+i.host:i.protocol+"//"+i.host}catch(e){}if(t.startsWith("/"))throw Error("Please provide a valid domain name");if(0===t.indexOf(".")&&(t=t.substr(1)),(-1!==t.indexOf(".")||t.startsWith("localhost"))&&!t.startsWith("http://")&&!t.startsWith("https://")){t="https://"+t;try{return new URL(t),e(t,!0)}catch(e){}}throw Error("Please provide a valid domain name")}(e)}},29996:function(e,t){"use strict";Object.defineProperty(t,"__esModule",{value:!0

My app info:

const appInfo = {
  appName: 'Lokalist Business',
  apiDomain: GET_FRONTEND_URL(),
  websiteDomain: 'dashboard.lokalist.mobile.app',
  apiBasePath: '/api/auth',
  websiteBasePath: '/auth',
}

export const GET_FRONTEND_URL = () => {
  if (process.env.NEXT_PUBLIC_APP_STAGE === 'production' && process.env.NODE_ENV === 'production') {
    return 'https://dashboard.lokalist.nl'
  }
  if (process.env.NEXT_PUBLIC_APP_STAGE === 'development' && process.env.NODE_ENV === 'production') {
    return 'https://staging-dashboard.lokalist.nl'
  }

  return 'http://localhost:2001'
}

What could it be? The origin is

capacitor://localhost

Heyy, We have a nest.js application deployed on Railway. In the frontend we have next.js deployed on Vercel. In the backend CORS is set like this

app.enableCors({
    origin: [
      '*',
      'http://localhost:3001',
      'http://localhost:3000',
      'https://*.vercel.app',
      'https://*.vercel.app/*',
    ],
    allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
    credentials: true,
  });

But for all the vercel preview builds, we can't test the app because of CORS issues. Any Idea how to fix it.??