Mark Lyck

This error seems to be back when using next-auth v5

Switching to `pnpm` seems to be a possible workaround. I was able to get past this error using `pnpm` but I'd be sad to give up using `bun` to be...

@balazsorban44 I still have this issue. But it's most likely an issue with either Vercel or Bun, and not `next-auth` itself.

I figured out what was causing the issue. In Vercel I had an environment variable `NODE_PATH` set to `./` I'm guessing there's an issue with Bun or Vercel that uses...

Thanks for posting this. I also had this error on `5.0.0-beta.19`. Downgrading to `5.0.0-beta.18` fixed it 👍

I patched the `next-auth` and `@auth/core` libraries with some more logs. This time i also deleted all of my browser history and cookies before the test. Here's the full sequence...

Interestingly, and possibly another bug? If I try the same login in incognito I get a different error: ``` [31m[auth][error][0m UnknownAction: Unsupported action. Read more at [https://errors.authjs.dev#unknownaction](https://errors.authjs.dev/#unknownaction) ``` I'm not...

Today I attempted to downgrade to `next-auth@4` to see if that worked, or at least provided more information. Downgrading to `next-auth@4` did resolve the `PKCE code_verifier cookie was missing..` error....

@ThangHuuVu Thank you for the response! And sorry the reply is a bit late, we can only deploy on Tuesdays and Thursdays to test this. Here are the browser cookies...

@ThangHuuVu @balazsorban44 Hmmm I believe we might have figured out the reason for this. For the affected clients, we have an HTTP proxy that opens a new HTTP connection to...