Missing or invalid Supabase environment variables

Hello,

I cannot seem to get anyone to actually help with this issue. I have multiple projects that have in the last two weeks decided to ignore the supabase env vars, even though they are present and available.

I have already checked them to make sure they are correct.

This morning I downloaded a zip of a project. Uploaded it to vercel. Created a new supabase instance, selected a west coast server, and created new tables, and still vercel does not recognize that the env vars are set.

It is the same as well for the blob store and the read and write token I have setup for storing images that come through a registration form in the project.

Screenshot 2025-09-08 at 11.03.20 AM

This is what I am seeing.

It seems to me that vercel is not seeing the variables, even though they are set. What would cause this? How do I fix it?

The biggest reason environment variables don't show as set is when you're accessing them from the client. Environment variables only exist server-side (but can be bundled into client code during build time if they're prefixed with NEXT_PUBLIC). Sometimes AI models will put code in the wrong environment and throw an error that looks like a missing environment variable but actually means some server code is running in the browser. This happens with supabase more often than other libraries because they have a lot of code that can also run client side and it isn't easy for LLMs to tell the difference

Can you give the name of the project or a chat ID so I can check the logs and see if there's anything strange going on?

Here is the project ID: pMTZdFAT0kK

Any help and insight you can give would be very appreciated!