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
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.
Configure the supabase.auth.signInWithOAuth method.
Ensure the Twitter provider has the correct redirect URI configured in the Twitter developer portal.
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.
The text was updated successfully, but these errors were encountered:
Hey there,
thanks for opening!
Can you confirm that you are requesting emails from users in your app in Twitter/X?
encima
added
auth
All thing Supabase Auth related
needs-analysis
Issue status is unknown and/or not possible to triage with the current info
and removed
bug
Something isn't working
labels
May 9, 2024
Bug Report
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:
supabase.auth.signInWithOAuth
method.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
^2.39.3
^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.
The text was updated successfully, but these errors were encountered: