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 OAuth stopped working #980

Open
1 of 2 tasks
Kylar13 opened this issue Feb 26, 2024 · 0 comments
Open
1 of 2 tasks

Twitter OAuth stopped working #980

Kylar13 opened this issue Feb 26, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Kylar13
Copy link

Kylar13 commented Feb 26, 2024

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

Twitter authentication stopped working, we get an error saying "No API key found in this request".

But the client library is initialized with the correct API keys and signing in with email still works, it's just Twitter that has stopped working.

To Reproduce

Configure a supabase client with the correct env variables and launch a twitter OAuth flow

Expected behavior

You get redirected to twitter and after to your callback route

Screenshots

fe48cfa0-e0af-4062-960e-8e330f918262

System information

  • OS: [e.g. macOS, Windows]
  • Browser (if applies) [e.g. chrome, safari]
  • Version of supabase-js: Happened with both "^2.39.3" and "^2.39.7" (Tried updating first to see if that was the issue)
  • Version of Node.js: Node 20 LTS
@Kylar13 Kylar13 added the bug Something isn't working label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant