Replies: 2 comments
-
@BluSimmon have you had any luck solving this by any chance? i just came across the very same problem testing Google OAuth provider |
Beta Was this translation helpful? Give feedback.
0 replies
-
https://next-auth-example.vercel.app/ works normally with v5.0.0-beta.25, can you try upgrade? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Provider type
Google
Environment
System:
OS: Windows 11 10.0.22621
CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11400F @ 2.60GHz
Memory: 2.87 GB / 15.87 GB
Binaries:
Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (122.0.2365.59)
Internet Explorer: 11.0.22621.1
npmPackages:
@auth/prisma-adapter: ^1.5.0 => 1.5.0
next: 14.1.1 => 14.1.1
next-auth: ^5.0.0-beta.15 => 5.0.0-beta.15
react: ^18 => 18.2.0
Reproduction URL
https://github.com/BluSimmon/next-auth-google
Describe the issue
The error screen after Login with Google
Error in terminal
How to reproduce
Expected behavior
Google OAuth works fine as other providers do.
Beta Was this translation helpful? Give feedback.
All reactions