-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NextAuth GitHub integration throws an error - refresh_token_expires_in
missing in Prisma schema
#182
Comments
Kind of agree with this. Maybe use Discord? Or just a simple Credentials-provider like the trpc/examples-kitchen-sink |
I think Discord is a good idea. |
For anyone seeing this error like me when trying github provider: you basically need to extend
I tested with only Github provider and it works, not sure with multiple providers. |
Describe the bug
When you scaffold a project with NextAuth and Prisma. Setting up the
env
file and using the GitHub provider throws an error as the Prisma Account schema is missing therefresh_token_expires_in
field. The NextAuth docs page suggests adding it to the schema.Exact error message:
To Reproduce
Steps to reproduce the behavior:
env
fileExpected behavior
The sign-in should succeed.
The default GitHub integration throwing an error can be confusing for someone new to NextAuth. I'm happy to create a PR and add the field to the schema if it makes sense. If we don't want to change the default Schema for NextAuth, it might make sense to explore another default provider instead of GitHub.
The text was updated successfully, but these errors were encountered: