Supertokens integrated with NestJs throws following error:

SuperTokens core threw an error for a GET request to path: '/apiversion' with status code: 404

Deployed through swarmpit

Hi, I'm using sendgrid to send mails with OTP and magic link. So sometimes user don't receive mails. So in that case I want to use default supertokens mailing system as a callback to this issue. Is that possible ?

I am getting an error when I do not explicitly set cookie_domain="localhost"

Hey, I'm receiving the following error. (I'm working on macOS) RuntimeError: asyncio.run() cannot be called from a running event loop sys:1: RuntimeWarning: coroutine 'Supertokens.send_telemetry' was never awaited RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Hi, is supertokens HIPPA compliant? We are looking at several companies and Auth0 i/ Microsoft are the only ones that seem to provide a Business Associate Agreement and PCI compliant environments.

Hello, Thank you for your product, it’s amazing how simple and comfortable it is to set up and use. Your work is breathtaking 🙂 But there’s one issue I ran into. Can you help? I’ve set up supertokens-python on FastAPI(0.95.1), and now I keep getting exceptions:

h11._util.LocalProtocolError: Can't send data when our state is ERROR

It seems that the root cause for it is inheritance from Starlette's BaseHTTPMiddleware https://github.com/encode/uvicorn/issues/111 https://github.com/encode/starlette/issues/1678 Can you help me in rewriting your middleware so it doesn’t use BaseHTTPMiddleware? Specifically, I have no idea what to do with

python
if result is None:
    response = await call_next(request)

I'm trying to get user name and surname following this section of the guide https://supertokens.com/docs/thirdparty/common-customizations/get-user-info where I should be able to access data with

override: {
                functions: (originalImplementation) => {
                    return {
                        ...originalImplementation,
                        // override the thirdparty sign in / up API
                        signInUp: async function(input) {
                            // TODO: Some pre sign in / up logic

                            let response = await originalImplementation.signInUp(input);

                            if (response.status === "OK") {
                                // This is the response from the OAuth tokens provided by the third party provider
                                let accessToken = response.oAuthTokens["access_token"];
                                // other tokens like the refresh_token or id_token are also 
                                // available in the oAuthTokens object.

                                // This gives the user's info as returned by the provider's user profile endpoint.
                                let firstName = response.rawUserInfoFromProvider.fromUserInfoAPI!["first_name"];

                                // This gives the user's info from the returned ID token 
                                // if the provider gave us an ID token
                                let lastName = response.rawUserInfoFromProvider.fromUserInfoAPI!["last_name"];
                            }

                            return response;
                        }
                    }
                }
            }

in the ThirdPartyEmailPassword.init() function in config.ts provided by the pre build code. Once here, what am I supposed to do to get name and surname? store it in metadata and then retrieve them through an api call?

I'm having an issue with integration with NestJS. I followed the guide in the documentation. But whenever I use the guard I get the following error.

Nest can't resolve dependencies of the AuthGuard (?). Please make sure that the argument Object at index [0] is available in the AppModule context.

The constructor for the guard looks like the following:

constructor(private readonly verifyOptions?: VerifySessionOptions)

It seems like the guard is having a DI issue and NestJS can't find it. Any helps on getting me int he right directino would be great.

Hi, when clicking on signout, or hitting any endpoint where we validate the session i get a inifinite loop of requests "try refresh token" cant figure out what's wrong

Hello everyone,

Server Error
TypeError: createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component

This error happened while generating the page. Any console logs will be displayed in the terminal window.
Call Stack
createContext
node_modules/.pnpm/supertokens-auth-react@0.33.1_react-dom@18.2.0_react@18.2.0_supertokens-web-js@0.6.0/node_modules/supertokens-auth-react/lib/build/userContextWrapper.js (13:48)
(sc_server)/./node_modules/.pnpm/supertokens-auth-react@0.33.1_react-dom@18.2.0_react@18.2.0_supertokens-web-js@0.6.0/node_modules/supertokens-auth-react/lib/build/userContextWrapper.js

I'm using NextJS App router, Do we have support of NextJS App router?