InvalidCheck: pkceCodeVerifier value could not be parsed. (Oath Provider Error)

[Lucifer472]

Provider type

GitHub, Google

Environment

System:
OS: macOS 15.1.1
CPU: (8) arm64 Apple M2
Memory: 305.41 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.1.0 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.8.3 - /opt/homebrew/bin/npm
bun: 1.1.38 - /opt/homebrew/bin/bun
Browsers:
Chrome: 131.0.6778.108
Safari: 18.1.1
npmPackages:
@auth/prisma-adapter: ^2.7.4 => 2.7.4
next: 15.0.3 => 15.0.3
next-auth: ^5.0.0-beta.25 => 5.0.0-beta.25
react: 19.0.0-rc-66855b96-20241106 => 19.0.0-rc-66855b96-20241106

Reproduction URL

https://github.com/Lucifer472/slack-clone

Describe the issue

[auth][error] InvalidCheck: pkceCodeVerifier value could not be parsed. Read more at https://errors.authjs.dev#invalidcheck
at parseCookie (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d_@auth_core_d1f52f..js:3030:15)
at Object.use (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d@auth_core_d1f52f..js:3058:30)
at handleOAuth (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d@auth_core_d1f52f..js:3288:247)
at async Module.callback (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d@auth_core_d1f52f..js:3782:41)
at async AuthInternal (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d@auth_core_d1f52f..js:4859:24)
at async Auth (/Users/truepubmedia/Desktop/sites/slack-clone/.next/server/chunks/e044d@auth_core_d1f52f._.js:5120:34)
at async AppRouteRouteModule.do (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:10:33313)
at async AppRouteRouteModule.handle (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/compiled/next-server/app-route.runtime.dev.js:10:40382)
at async doRender (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:1455:42)
at async responseGenerator (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:1814:28)
at async DevServer.renderToResponseWithComponentsImpl (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:1824:28)
at async DevServer.renderPageComponent (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:2240:24)
at async DevServer.renderToResponseImpl (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:2278:32)
at async DevServer.pipeImpl (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:960:25)
at async NextNodeServer.handleCatchallRenderRequest (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/next-server.js:281:17)
at async DevServer.handleRequestImpl (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/base-server.js:853:17)
at async /Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/dev/next-dev-server.js:373:20
at async Span.traceAsyncFn (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/trace/trace.js:153:20)
at async DevServer.handleRequest (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/dev/next-dev-server.js:370:24)
at async invokeRender (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/lib/router-server.js:183:21)
at async handleRequest (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/lib/router-server.js:360:24)
at async requestHandlerImpl (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/lib/router-server.js:384:13)
at async Server.requestListener (/Users/truepubmedia/Desktop/sites/slack-clone/node_modules/next/dist/server/lib/start-server.js:142:13)

Credentials Provider works like charm without any issues but Oath Providers are not working all the give the same error i tried different ways to sort it out but nothing works. i think the issue is with latest version on next js and prisma because i tried going to past version but same issue also the same config works perfectly fine in next js 14 i tried that

How to reproduce

Just clone the repo and added github client id and secret in env file also connect a database

Expected behavior

Github provider should redirect to authorized page then logged in to App.

[OtisTemler]

Same issue here, using Next.js 15.1.0 & React 19.

Sometimes works, sometimes doesn't with the above stated error.

[pr-citrate]

I encountered the same issue as you described with Next 15.1 and React 19.0. If you’ve found any potential workarounds or additional details since your post, I’d appreciate it if you could share them here!

[junheeLee96]

I also encountered the same error. In my case, I used Chrome's incognito mode to log in and found that the error disappeared.

[rubinpaudel]

I have the same issue with Notion, using these versions:

"next": "15.1.2",
"next-auth": "5.0.0-beta.25",
"react": "^19.0.0",

[Harisene]

I have the same issue. I get this error when I try to log in using google provider.

�[31m[auth][error]�[0m InvalidCheck: pkceCodeVerifier value could not be parsed. Read more at https://errors.authjs.dev#invalidcheck

20:24:42.971
at i8 (/var/task/.next/server/chunks/555.js:368:26741)
    at Object.use (/var/task/.next/server/chunks/555.js:368:27149)
    at os (/var/task/.next/server/chunks/555.js:368:33213)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async ob (/var/task/.next/server/chunks/555.js:368:40282)
    at async oR (/var/task/.next/server/chunks/555.js:368:51845)
    at async oC (/var/task/.next/server/chunks/555.js:368:56536)
    at async te.do (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:17826)
    at async te.handle (/var/task/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:18:22492)
    at async eB (/var/task/node_modules/next/dist/compiled/next-server/server.runtime.prod.js:2871:21083)

I use,

"react": "19.0.0-rc-66855b96-20241106",
"next": "15.0.3",
"next-auth": "^5.0.0-beta.25"

[suitux]

Same here

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[Lucifer472]

well downgraded to next 14.2.20 and next auth beta to 5.0.0-beta.20 and everything if fixed and also clear your cookies as well.

[Ferdinand737]

well downgraded to next 14.2.20 and next auth beta to 5.0.0-beta.20 and everything if fixed and also clear your cookies as well.

Doing this did not solve the issue for me.

[Harisene]

well downgraded to next 14.2.20 and next auth beta to 5.0.0-beta.20 and everything if fixed and also clear your cookies as well.

Doing this did not solve the issue for me.

Same here. Issue still exists

[wouteth]

Also experiencing the same issue. It occurs randomly on sign in. Some sign-ins work, some throw this exact error.

[stephan-noel]

Same happening for me using the Cognito provider. Works most of the time but getting these errors in the logs and some users saying they can't log in. Please let me know if there's any other info I can provide to help out.

"next-auth": "5.0.0-beta.20"
"next": "14.2.22",
"react": "18.3.1"