I get the following error when i try to sign up with a user: Error: No SuperTokens core available to queryError: No SuperTokens core available to query Setup: I am self hosting a core, without docker on my mac. (It should be running, i can get the hello message when visiting /hello) The connection to my postgresql is successful (the default supertokens tables have been generated)

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",

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.

Good morning from Sweden! I am using a setup of supertokens consisting of passwordless (phone verified login) and sessions. My stack also consists of Nest.js and Hasura. I've implemented JWTs according to your documentation, and it has mostly worked really well. However, there's one issue. Every now and then, all the JWTs generated and sent for verification to Hasura are treated as invalid. When this happens, the only solution I've found is to restart the Hasura instance so that it refetches the JWK via the jwk_url. Once this is done, it starts working again. It seems that this issue coincides with either an update of the JWK in our backend or a change in our backend deployment to use a newer version. I am assuming that Hasura remains unaware and doesn't attempt to refetch a new valid JWK. I'm unsure if there's an error in my implementation or if this is a bug. Any help would be appreciated.

Hello, I'm using supertokens within my flask application using https://github.com/supertokens/supertokens-python This is a short example of my code: from supertokens_python.framework.flask import Middleware app = Flask(__name__) init_supertokens(app) Middleware(app) CORS(app=app, origins=[app.config.get('WEBSITE_DOMAIN', '')], supports_credentials=True, allow_headers=["Content-Type"] + get_all_cors_headers()) I was trying to add flask_socketio using the following code:

from flask_socketio import SocketIO

SocketIO(app)

But than I came across asyncio issues(Added image of the error) It seems that there is a clash between the socket io event loop and the supertokens asyncio, can you please recommend the best practice of how to integrate flask_socketio while I already have supertokens installed on my flask? Thanks!

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

Getting this error:

TypeError: this.response.status is not a function

, used to work fine but now this.

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

@bradvrm Moving this to a separate thread

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)