Getting this error:

TypeError: this.response.status is not a function

, used to work fine but now this.

Are you manually sending a custom response from an api override? Can you share the code please?

I've made a lot of API overrides, my backend config is in the attached file

Also, when you say that it used to work fine, but isn’t now - is that cause you did a version update to the backend SDK? Or just updated your code?

I didn't touch it for weeks, I tried updating the SDK to fix it but that didn't fix it. It wasn't caused by an update to the backend SDK. But NPM might have decided to autoupdate it, not sure. But it errors inside the supertokens-node library when attempting to send a JSON response

Which part of the file you shared does the error come from?

I'm not sure, the stacktrace doesn't give any clue about where the error comes from but its alteast in Supertokens-node's error handeling. I'll take a look in the logging system to see if I can find something there

Which version of express are you using?

NextJS ^12.2.5

I’m talking about the supertokens middleware. Not the verifySession function

I'll check that once I can login to my app, i'm locked out at the moment

The api folder -> the /auth/* route

Ah, the contents of that file is:

ts
import { superTokensNextWrapper } from 'supertokens-node/nextjs'
import { middleware } from 'supertokens-node/framework/express'
import { NextApiRequest, NextApiResponse } from 'next'
import { Request, Response } from 'express';
import supertokens from 'supertokens-node'
import { backendConfig } from '../../../config/backendConfig'
import NextCors from "nextjs-cors";

supertokens.init(backendConfig())

export default async function superTokens(
    req: NextApiRequest & Request,
    res: NextApiResponse & Response
) {

    let origin = *origin mess here*

    // NOTE: We need CORS only if we are querying the APIs from a different origin
    await NextCors(req, res, {
        methods: ["GET", "HEAD", "PUT", "PATCH", "POST", "DELETE"],
        origin,
        credentials: true,
        allowedHeaders: ["content-type", ...supertokens.getAllCORSHeaders()],
    });

    await superTokensNextWrapper(
        async (next) => {
            await middleware()(req, res, next)
        },
        req,
        res
    )
    //if (!res.writableEnded) {
    //    res.status(404).send('Not found')
    //}
}

Ok thanks. I’ll wait for this answer.

When logging requests with Safari devtools the only red items I see are to my own API endpoind, contents being:

ts
import { superTokensNextWrapper } from 'supertokens-node/nextjs'
import { SessionRequest } from 'supertokens-node/framework/express'
import { verifySession } from "supertokens-node/recipe/session/framework/express";
import { NextApiRequest, NextApiResponse } from 'next'
import { Request, Response } from 'express';
import supertokens from 'supertokens-node'
import { backendConfig } from '../../config/backendConfig'
import NextCors from "nextjs-cors";
import UserMetadata from 'supertokens-node/recipe/usermetadata'

supertokens.init(backendConfig())

export default async function userData(
    req: NextApiRequest & Request,
    res: NextApiResponse & Response
) {

    await superTokensNextWrapper(
        async (next) => {
            await verifySession()(req, res, next)
        },
        req,
        res
    )

    const session = (req as SessionRequest).session;

    if (session == undefined) {
        res.status(401).send("Unauthorized")
        return
    }
    const userId = session!.getUserId();

    const { metadata } = await UserMetadata.getUserMetadata(userId);

    res.json(metadata)

}

But Safari being Safari it didn't log any response info, I'll try Chrome

Ahh I see. So that auth APIs and overrides work

I think so. When logging in I do get sent back to the login screen

So you get back a 401 from the api? Or a 500?

401

So you get a 401 and the error stack you sent above? (About the function not found)

Yes

Does the 401 result in calling the refresh api from the frontend and that causes the error stack above?

After the failed API call it goes directly to the login page without any other endpoints called

Can you do a console log in your api right before the const session = …. line? Does that log get printed out?

It does reach

if (session == undefined) {

, but after that it just fails and the client redirects to login (which is my code).

Hmm. This whole thing is very strange. I’m not sure what the issue is

Yes, using the VSCode debugger I've found this error:

Exception has occurred: Error: Session does not exist. Are you sending the session tokens in the request with the appropriate token transfer method

during login. And the request to my userdata api endpoint doesn't have any Cookies or other data attached to it

So that’s another problem. But first we need to figure out why that function not found stack trace is showing up at all.

I'll open it tommorow as its also quite late here. Good night

ok thanks!