Twitter external provider (Error getting user email)

[Ahmed14z]

Bug Report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

The Twitter OAuth provider is not functioning correctly on both localhost and hosted environments. Similar to a previously documented issue where Twitter OAuth operates on hosted instances but fails on localhost, in my case, the provider fails in all environments.

To Reproduce

Steps to reproduce the behavior:

1. Set up Twitter OAuth on local development server (e.g., http://localhost:8000).
2. Configure the supabase.auth.signInWithOAuth method.
3. Ensure the Twitter provider has the correct redirect URI configured in the Twitter developer portal.
4. Attempt to sign in using the signInWithOAuth method and observe the error on the redirect page: error=server_error&error_code=500&error_description=Error+getting+user+email+from+external+provider#error=server_error&error_code=500&error_description=Error+getting+user+email+from+external+provider.

Expected behavior

I expect the Twitter OAuth provider to allow users to sign in successfully, creating a user session without issues, in both development and production environments.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• Version of supabase-js: ^2.39.3
• Version of Node.js: ^10.9.2

Additional context

This issue appears on both local development and hosted setups, unlike the other issue where it was restricted to local development only.

[encima]

Hey there,
thanks for opening!
Can you confirm that you are requesting emails from users in your app in Twitter/X?

[simonha9]

Hi, I am unable to repro this, following the guide here doing a full pkce flow,

[Ahmed14z]

Yes as @encima described it worked when i enabled it , thanks!