Skip to content
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

Twitter signup error: Error getting user email from external provider #100

Closed
magoz opened this issue May 17, 2022 · 6 comments
Closed

Twitter signup error: Error getting user email from external provider #100

magoz opened this issue May 17, 2022 · 6 comments

Comments

@magoz
Copy link

magoz commented May 17, 2022

The 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:

supabase1

supabase2

Am I doing something wrong?
What's the right way of setting up Twitter Oauth?

@thorwebdev
Copy link
Member

This is unrelated to the helpers lib, please see here: supabase/auth#214

@magoz
Copy link
Author

magoz commented May 17, 2022

Thanks @thorwebdev ! I'll look into it and the Supabase main repo and Discord.
The Twitter user I'm testing with has an email linked.

@magoz
Copy link
Author

magoz commented May 17, 2022

Just in case somebody else has the same problem. I solved it by applying to Elevated access.

@ervinismu
Copy link

hi @magoz i have same issue with github login, any reference for github login?

@magoz
Copy link
Author

magoz commented Sep 12, 2022

hi @magoz i have same issue with github login, any reference for github login?

No, sorry @ervinismu , I didn't use GitHub login.

@ethanchiasson
Copy link

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...

Screen Shot 2022-09-14 at 1 26 14 PM

Screen Shot 2022-09-14 at 1 26 36 PM

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants