Is there a way out of the box to catch 'invalid_grant' callback error for Google Provider

[dragGH102]

If OAuth callback error throws 'invalid_grant' the sign-in flows (gets stuck at Google account select screen).
JWT callback is called even if that error happens.

how would I reproduce this error anyway to see if I get the error in the JWT callback somehow?
It happened once, lasted for ~2-3 hours after many tries, and solved itself afterward. and it has never happened again.

The main goal of the question/discussion is understanding how to handle this eventuality so the auth flow doesn't break if it happens, ie invalidating the session or the sort

I have implemented token rotation - is that enough to prevent this situation?

[sudhanshubsr]

[next-auth][error][OAUTH_CALLBACK_ERROR]
https://next-auth.js.org/errors#oauth_callback_error invalid_grant (Bad Request) {
error: OPError: invalid_grant (Bad Request)
at processResponse (webpack-internal:///(rsc)/./node_modules/openid-client/lib/helpers/process_response.js:34:19)
at Client.grant (webpack-internal:///(rsc)/./node_modules/openid-client/lib/client.js:1206:28)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Client.callback (webpack-internal:///(rsc)/./node_modules/openid-client/lib/client.js:418:30)
at async oAuthCallback (webpack-internal:///(rsc)/./node_modules/next-auth/core/lib/oauth/callback.js:118:22)
at async Object.callback (webpack-internal:///(rsc)/./node_modules/next-auth/core/routes/callback.js:18:79)
at async AuthHandler (webpack-internal:///(rsc)/./node_modules/next-auth/core/index.js:202:38)
at async NextAuthRouteHandler (webpack-internal:///(rsc)/./node_modules/next-auth/next/index.js:50:30)
at async NextAuth._args$ (webpack-internal:///(rsc)/./node_modules/next-auth/next/index.js:85:24)
at async C:\Users\sudha\OneDrive\Desktop\Portfolio\PortFolio Projects\feedback-board\node_modules\next\dist\compiled\next-server\app-route.runtime.dev.js:6:63251 {
name: 'OAuthCallbackError',
code: undefined
},
providerId: 'google',
message: 'invalid_grant (Bad Request)'
}

Is this same happening with you!

Not able to resolve it tried everything

[aomini]

I'm having the same issue. Not sure why it's happening

[chanhyokpark]

I'm having the exact same issue. The log says:

[next-auth][error][OAUTH_CALLBACK_ERROR] 
https://next-auth.js.org/errors#oauth_callback_error invalid_grant (Bad Request) {
  error: OPError: invalid_grant (Bad Request)
      at processResponse ((project dir)/node_modules/openid-client/lib/helpers/process_response.js:38:13)
      at Client.grant (.../node_modules/openid-client/lib/client.js:1354:22)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async Client.callback (.../node_modules/openid-client/lib/client.js:493:24)
      at async oAuthCallback (.../node_modules/next-auth/core/lib/oauth/callback.js:109:16)
      at async Object.callback (.../node_modules/next-auth/core/routes/callback.js:52:11)
      at async AuthHandler (...node_modules/next-auth/core/index.js:208:28)
      at async NextAuthApiHandler (.../node_modules/next-auth/next/index.js:22:19)
      at async NextAuth._args$ (.../node_modules/next-auth/next/index.js:108:14)
      at async K (.../node_modules/next/dist/compiled/next-server/pages-api.runtime.prod.js:20:16853) {
    name: 'OAuthCallbackError',
    code: undefined
  },
  providerId: 'google',
  message: 'invalid_grant (Bad Request)'
}

jwt callback is called after that error, and it only happens on production. Turning on debug didn't return any useful information. This error happens randomly, and I can't figure out why.

[sudhanshubsr]

I was able to resolve it, but don't remember how, i will post here if I remember something.

[SW-Wanted]

Could you post here how do you solve it @sudhanshubsr ?

[chanhyokpark]

I somehow figured it out but forgot about this thread. For me, it was misconfigured service worker trying to cache oauth callback page, resulting the token to be consumed by SW.

[SW-Wanted]

Can anyone help me? I have the same error message that you describe.