Hello, Sometimes i am getting the error

supertokens_python.exceptions.GeneralError: No SuperTokens core available to query

. Is this caused by network issues? (i am using the managed service)

Hello, i need to configure the backend for to accept capcitor://app.id URL and not only http or https. Someone can help me?

Hello, I'm trying to authorize with Twitter Oauth2, her's my custom provider config:

{
          config: {
              thirdPartyId: "twitter",
              name: "Twitter",
              clients: [{
                  clientId: twitterClientId,
                  clientSecret: twitterClientSecret,
                  scope: ["users.read"]
              }],
              authorizationEndpoint: "https://twitter.com/i/oauth2/authorize",
              tokenEndpoint: "https://api.twitter.com/2/oauth2/token",
              UserInfoEndpoint: "https://api.twitter.com/2/users",
          }
        }

I'm using core5 and the follow version of the npm packages: frontend: "supertokens-auth-react": "0.31.0", "supertokens-web-js": "0.5.0", backend: "supertokens-node": "^13.6.0",

Hi 👋 . I'm setting up supertokens with Next.js for the first time and have a basic question. In SSR setup (https://supertokens.com/docs/thirdparty/nextjs/session-verification/in-ssr), the "needs-refresh" prop is added so that would "force the frontend to try and refresh". Is there a way for this to be done on the server? If done on the FE, I think that means SSR isn't really working as it should.

Has anyone had this problem? It happens constantly, but the user just needs to try to login/request again and it works.

Think I might have a bug report regarding user meta/the dashboard. I'm using ThirdPartyEmailPassword receipie in my FE and BE configs. And UserMeta/Dashboard in my BE config When I go to the dashboard to edit a users name and click save I get these logs:

Error: Initialisation not done. Did you forget to call the SuperTokens.init function?
at Function.getInstanceOrThrowError (/app/node_modules/supertokens-node/lib/build/recipe/emailpassword/recipe.js:199:15)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:76:18
at Generator.next (<anonymous>)
at /app/node_modules/supertokens-node/lib/build/recipe/dashboard/api/userdetails/userPut.js:30:75
at new Promise (<anonymous>)

But when I refresh the dashboard, the meta has actually saved

Hi, i try to use supertokens on nuxtjs with nuxt-auth. i have write a custom scheme extends cookies scheme. The question is, can i use "sIRTFrontend" to determine whether the session is alive on the middleware checking?

I have an issue with refreshing tokens with Next'js & Nest.js. I have followed guide for Sessions with Server Components: https://supertokens.com/docs/thirdparty/nextjs/app-directory/protecting-route#sessions-with-server-components--pre Everything works fine until the access token expires and new one has to be issued. Then at this moment I receive an error that prevents anything from rendering.

Warning: Functions are not valid as a React child

Refreshing the page afterwards with a valid access token doesn't cause issue. This stacktrace also mentions

SessionAuth

component, which makes me suspect that it's problem with the SuperTokens itself. Let me write this step by step what happens: 1. Refresh token epxires. 2. Browser sends two requests to:

/auth/session/refresh

and then

/auth/session/verify

(but not always). Response status codes are

200

3. While these requests happen, nothing is being rendered. These requests set the cookies accordingly. Error pasted below. 4. Refreshing site once again makes everyghing "just appear" and application behaves as desired. I have tried lowering the time

ACCESS_TOKEN_VALIDITY

environment variable to a few seconds to make sure that it's the invalid access token that causes trouble.

Hey! I am trying to customise the Signup / Signin forms using the

ThirdPartyEmailPassword

recipe via the

supertokens-auth-react

package. When implementing the

EmailPassword

recipe I can already customise the entire form page (e.g. creating custom backgrounds, images, etc..) like so:``` <EmailPasswordComponentsOverrideProvider components={{ EmailPasswordSignIn_Override: ({ DefaultComponent, ...props }) => { return ( // My custom Signin component ); }, EmailPasswordSignUp_Override: ({ DefaultComponent, ...props }) => { return ( // My custom Signup component ); }, }} > ``` However, when I try to achieve the same using the

ThirdpartyEmailPasswordComponentsOverrideProvider

it seems I can only customise some parts of the form (e.g. footer, etc..). Any suggestions ? Thanks 🙂

SESSION STILL AVAILABLE AFTER REVOKING IT