Twitter signup error: Error getting user email from external provider
See original GitHub issueThe docs for setting up Twitter Login are outdated.
The 3-legged OAuth is no longer available.
I’ve tried what was suggested in this discussion.
The authentication redirection works but when I get back to my app I get the following http://localhost:3000/?error=server_error&error_description=Error+getting+user+email+from+external+provider
Her is my setup:
Am I doing something wrong?
What’s the right way of setting up Twitter Oauth?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Twitter OAuth signup fails if user has no email on ... - GitHub
If a twitter user doesn't have their email address connected to their twitter account, supabase's twitter OAuth integration fails on signup with ...
Read more >How to fix Twitter email or phone number already in use
Trying to create an account on Twitter but see a message saying your email address, username, or phone number are already in use?...
Read more >Getting the email from external providers Google and ...
I see the email address for both Facebook and Google in the debugger. ... Sign in the user with this external login provider...
Read more >Not returning User's Email address in External Callback
Hi @systems_app,. Last month we announced a new requirement that any developer using Sign in with Twitter must explicitly declare their callback ...
Read more >External provider email is missing error is thrown when ...
According to the following link https://developers.facebook.com/bugs/298946933534016 which is a bug item logged at Facebook Developers, some ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just in case somebody else has the same problem. I solved it by applying to Elevated access.
I am still getting this error even after updating to elevated status.
Also, my Twitter Developer UI looks a little different now…
I am not sure why I am still getting this error even after updating to elevated status.
Any ideas to why this would be happening ?