Bug: Supabase integration uses outdated user email

Feedback
,
1

I found a bug with supabase integration.

I have a supabase database I’d like to connect to. However:

  1. Vercel does not see it, only offering to create a new DB.
  2. Upon creating a new one, it does so in a different supabase workspace, under my old email address.

Note that:

  1. I have removed the address from supabase entirely already.
  2. I am using GitHub OAuth to log in to both supabase and vercel, with the same account.
  3. The github account did have the old email until a few months ago. Now I only use the new email address everywhere - both in Vercel, GitHub, Supabase.

What I’ve tried:

  1. I have refreshed my GitHub authentication in Vercel
  2. I have logged in again, in hopes it would refresh my session / clear the cache
2

I’ve disconnected the supabase integration. Reconnecting it seemingly refreshes the email, but does not see existing projects or DBs. Upon visiting supabase, the page throws the following error:

{"message":"{\"code\":500,\"error_code\":\"unexpected_failure\",\"msg\":\"Multiple accounts with the same email address in the same linking domain detected: default\",\"error_id\":\"82f1e000-b561-4389-862e-284b1a8f9388\"}"}
3

I have connected to the DB by specifying the variable manually.

4

Thanks for reporting this. I shared this info with the team so we can investigate. Glad to hear you found a temporary workaround with the manual variable value

1 Like
6

Hey @linasko. I’ve heard back from our integrations team and contacts at Supabase. If you reach out to Supabase support they’ll be able to get this sorted. You can share a link back to this conversation for context.

Thanks for letting us know about this, and for your patience while we investigated

7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.