Next-auth: [v2] Server And Client Stops And Throws Error When GitHub Does Not Send Email ID
I have privacy enable on github so it does not send email.
I get this error and both server and client stops working.
SabariVig
All 4 comments
You can check out #131. We currently don't support signing up without email address but we're looking into supporting this.
LoriKarikari
on 21 May 2020
It would be better if the user get some response .instead of an error
SabariVig
on 21 May 2020
Absolutely!
The plan for launch is to require an email address - as there are a few considerations that arise from not doing that and I'd rather not worry about them all now - but it should definitely be handled gracefully, and just ask the user for an email address (and not error).
This should be fixed soon.
iaincollins
on 23 May 2020
hey @iaincollins wanted to also ask about this feature: to be able to sign in with GitHub even if an email is not on the users GitHub public profile. When signing in with GitHub on the next-auth demo (I do not currently have a public email on my GitHub), I was given this message which you merged as part of #152
Sign in with another account
Your account doesn't have an email address (required).Try signing in with a different account.
I know this is how you are handling it in the short term but I am thinking of using next-auth with GitHub for my primary auth provider and want to see if there were further plans to try and remedy this issue for people who do not have public emails on their GitHub profile. I think this would be kind of a bigger deal for my use case as for now I am only planning on using GitHub as auth strategy.
shufflemattdev
on 7 Jun 2020
Related issues
ryanbahan
路
3Comments
MelMacaluso
路
3Comments
Xetera
路
3Comments
ryanditjia
路
3Comments
dmi3y
路
3Comments
Most helpful comment
hey @iaincollins wanted to also ask about this feature: to be able to sign in with GitHub even if an email is not on the users GitHub public profile. When signing in with GitHub on the next-auth demo (I do not currently have a public email on my GitHub), I was given this message which you merged as part of #152
I know this is how you are handling it in the short term but I am thinking of using next-auth with GitHub for my primary auth provider and want to see if there were further plans to try and remedy this issue for people who do not have public emails on their GitHub profile. I think this would be kind of a bigger deal for my use case as for now I am only planning on using GitHub as auth strategy.