Supabase not working in prod for Vercel web app

[mitraraman]

I have a web app that I've deployed to Vercel and using Supabase for database and auth (email and Google). Google auth is working just fine, but email auth and any database functions are not working. They're just not calling for some reason. This is only happening in Prod, and there are no logs or errors to look into. It works perfectly fine locally. FWIW, this was working in Prod until recently and I didn't make any changes to auth / Supabase code (as far as I can tell) to cause this issue.

[ethanszeto]

Hi! I've encountered a similar issue and am still trying to find a solution. Here's what I've uncovered so far:

• Logs and Auth Token: I've checked both Vercel and Supabase logs and confirmed that the Supabase auth token is being passed correctly from the middleware to the serverless functions in my Vercel deployment.

• Supabase Logs: However, when I check the Supabase logs for those exact requests, they don't seem to have any associated auth_user. This is strange because the same requests sent locally are logged correctly on Supabase with the expected auth_user, and they return the expected data.

• Environment Consistency: This issue is affecting my production environment and also happens on Vercel Preview deployments. Locally, everything works fine, so it seems tied to how the production or preview environments are interacting with Supabase.

What configuration and where are you executing your Supabase queries? (i.e. edge middleware, serverless fcns, etc)
Does this happen for you on Preview or just strictly Prod?
When did you start encountering this issue? For me this started middle of last week.

Let me know if you've observed similar things, since this issue has been plaguing me for quite some time. Also anyone else, help would be appreciated.