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 everyone, I wanted to implement social login with custom UI, but i am getting below error auth.service.ts:24 GET http://localhost:8000/api/auth/authorisationurl?thirdPartyId=google&redirectURIOnProviderDashboard=http%3A%2F%2Flocalhost%3A8000%2Fauth%2Fcallback 400 (Bad Request) {"message":"the provider google could not be found in the configuration"} i am using fastapi for backend and angular for frontend fastapi this is my RecipeList RECIPE_LIST = [ session.init(), thirdpartyemailpassword.init( sign_up_feature = thirdpartyemailpassword.InputSignUpFeature( form_fields=[InputFormField(id='email'), InputFormField(id='password'), InputFormField(id='firstName'), InputFormField(id='lastName'), InputFormField(id='phone') ], )), thirdparty.init( sign_in_and_up_feature=thirdparty.SignInAndUpFeature(providers=[ ProviderInput( config=ProviderConfig( third_party_id="google", clients=[ ProviderClientConfig( client_id="1060725074195-kmeum4crr01uirfl2op9kd5acmi9jutn.apps.googleusercontent.com", client_secret="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", ), ], ) ) ]) ), dashboard.init() ]

Hi I've got a problem with Angular + Capacitor + Supertokens. In the web version everything works perfectly but when I test the app in iOS for example, then after the login the refresh call of doom is starting 😄

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", 
            }
          });

I'm getting this error: SuperTokens core threw an error for a POST request to path: '/recipe/session/regenerate' with status code: 400 and message: The user payload contains protected field My code looks like this:

await session.mergeIntoAccessTokenPayload({ sessionHandle: session.getHandle() });

How can I go about debugging this?

Hey all. My company is looking to transition over to SuperTokens. After looking at some things we see that our current auth solution uses PKCE, but it appears that SuperTokens does not support OAuth 2.0 flows, but that does not seem quite right to me. Would someone be able to point me towards the proper documentation to answer this question?

hello guys! question: is there any way to include supertokens API into general swagger-based API docs of the project? i use nest.js and connected via middleware, so maybe it's not possible or maybe you know how to do it?

Hi, I'm looking for some clarification on the pricing change that seemed to happen March 18th. Is multi-factor authentication support via SMS something that we will be charged for even if we aren't using SuperToken's sending services? We're using our own service to send the text message after overriding the

smsDelivery

function, under the

Passwordless

recipe, and we were not expecting the new $100/month price minimum.

Hi, I am trying to integrate Supertokens with echo-labstack. I followed this example https://github.com/supertokens/supertokens-golang/blob/master/examples/with-labstack-echo/main.go. Echo advocates to return errors from your Handlers, which will then be handled by their HTTP Error Handler (which you can customize). This works fine until I introduce the session.VerifySession in my middleware, as per the example (wrap it to turn it into a echo.MiddlewareFunc). As soon as I use this middleware on my routes, they always return

200

(empty body), no matter how may errors I return from my handlers. As soon as I remove the session.VerifySession echo'fied middleware, I get the actual errors. It seems as if the session.VerifySession middleware is swallowing the echo error and just returning a

200

instead. Anybody any idea what could be causing this?

Hi, I'm experiencing a problem with the get_user_by_id method from supertokens_python.recipe.thirdparty.syncio. When I access this API route, I get the error message "Initialisation not done. Did you forget to call Supertokens.init". But the rest of the app is working fine (also with login/ logout etc., acccessing the session). Is there something I need to change for the API view?

@method_decorator(verify_session(), name='dispatch')
class UserIsThirdParty(APIView):

    def get(self, request: HttpRequest):
        session: SessionContainer = request.supertokens

        user_id = session.get_user_id()

        user = get_user_by_id(user_id)
        ...