You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the email is set to notNull for compatibility with NextAuth adapter, some Github users might not be able to login due to a setting on their profile: Keep my email addresses private - when checked Github returns null for the email, hence not allowing you to write to the model.
The text was updated successfully, but these errors were encountered:
I had to update the permissions within the github app I created for authentication within settings -> developer settings -> my app -> Permissions. Once this was updated the email address started getting populated in the Auth response
This makes more sense to me, as even when dealing with 3rd party OAuth flows, 99% of the time I always request the email scope anyway.
Just echoing this, I also had to add the email scope, would be great if we could add this step to the guide: https://vercel.com/guides/nextjs-multi-tenant-application
And also deprecate step 3 (publishing Prisma schema) now Drizzle is being used.
As the email is set to notNull for compatibility with NextAuth adapter, some Github users might not be able to login due to a setting on their profile: Keep my email addresses private - when checked Github returns null for the email, hence not allowing you to write to the model.
The text was updated successfully, but these errors were encountered: