5 people reported
All time, since May 27.
GitHub login opens empty account
“I am a Pro tier customer currently completely locked out of my account due to a GitHub OAuth routing error.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/supabase/issues/8875/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
GitHub sign-in opens a new empty account, not existing org. Logging in via GitHub routes to "a new, blank Supabase account setup page" with no projects, locking out paid Pro organizations.
Is this your bug?
File my report- Where
- GitHub OAuth login
- How bad
- Stops work: a core feature can't be used. Some reports say it blocks them completely.
Not quite your bug?
- MFA prompt never enrolled9 people
- GitHub sign-in multiple accounts error3 people
- Project disappears from dashboard2 people
Original reports5, newest first
- URGENT: Existing Supabase organisation/project disappeared — SU-475662 unanswered for 2+ weeks#51063
- Unlink GitHub OAuth#48868
- Impossible d'accéder à mon projet PRO payant : compte incorrect après la connexion à GitHub#47810
- Urgent: Pro Account Lockout (OAuth Bug) — Need Manual Escalation Ticket SU-408313 and SU-408269#47464
- I can't access my paid sup-abase projects account#46432