[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live) [v0](/c/v0/59) # Missing environment variables in v0 331 views · 16 likes · 17 posts AH7128 (@alexhandsaker-7128) · 2025-11-21 · ♥ 2 I’ve been constantly having issues with my app throughout today, and now I’m getting this:  Not only was it straight after making a completely unrelated change to my app, but going back to a previous part in the chat throws the exact same error. I have not deployed it the latest change, nor have I made any changes to Github or Supabase I cannot for the life of me understand why PREVIOUS versions are now throwing up this issue It now means that I can’t log into my app in preview - This issue does not persist into my deployed version of the app This is what I get when I try and login through the auth screen of my app in preview  What is going on? AH7128 (@alexhandsaker-7128) · 2025-11-21 · ♥ 1 I have a separate app connected to the same supabase DB and I’m getting an error in there in the preview also  Nothing connecting or pulling through, it’s entirely broken Voyager (@voyagermsp) · 2025-11-21 I just logged in to my app and getting same message. Then I checked v0 previous env variables and they are all missing! Looks like there was a UX update and maybe some of us lost our env vars?  AH7128 (@alexhandsaker-7128) · 2025-11-21 · ♥ 2 I’ve logged into another laptop, into a completely separate V0 account where I’m working on a different app (completely different supabase etc.) This looks like it’s a V0/Verce issue and I think I’ve wasted about £10 in credits chasing these issues over the last couple of days, and lost a couple of days of progress also. AH7128 (@alexhandsaker-7128) · 2025-11-21 · ♥ 2 Yes that account that i’ve just logged into says no account variables also AH7128 (@alexhandsaker-7128) · 2025-11-21 · ♥ 2 Oh wait it’s this one also bloody marvelous - I sure hope they have backups….  Honestly at this point I’m considering moving over to lovable, and I’ve been with V0 since January with multiple accs. it’s infuriating the amount of money I’ve spent chasing errors in my app that were actually errors with V0. Maybe time for Lovable/Base44/Replit Voyager (@voyagermsp) · 2025-11-21 It’s definitely a v0 interface bug, I can’t re-add my vars either, they keep disappearing as soon as I add them in. Logging support ticket. Pauline P. Narvas (@pawlean) · 2025-11-21 · ♥ 2 Hi, everyone! Thank you for flagging. I've shared this with the v0 team and will loop back with updates ASAP. Appreciate your patience :folded_hands: AV9706 (@andreasvourkos-9706) · 2025-11-21 Environment variables got lost suddenly from all projects, please fix Joachimber 8510 (@joachimber-8510) · 2025-11-21 · ♥ 1 Same here, +1 This really doesn’t look for people who want to launch a real project with Vercel… Joachimber 8510 (@joachimber-8510) · 2025-11-21 I really hope there’s a backup lol because I cannot remember every single environment variable I used… Joachimber 8510 (@joachimber-8510) · 2025-11-21 All my environment variables are suddenly gone, and if I add a new variable it immediately disappears. Anyone else having this issue? My Supabase variables, Google auth variables, AI API keys, everything just gone. rothnic (@rothnic) · 2025-11-21 Same for me. Setup new v0 project, added supabase, then got the error about missing the next public env variables to connect to supabase. Manually added the env variables doesn’t work. Like you said, they show momentarily until the app reloads, then they are gone again. Jerry 2306 (@jerry-2306) · 2025-11-21 v0 environment has been glitchy since yesterday. came in today to the missing variables issues. As of right now the variables are back but they are not accessible to the environment, the following message. The environment variables ARE listed but NOT accessible in the Next.js Edge Runtime. Pauline P. Narvas (@pawlean) · 2025-11-21 · ♥ 1 Our engineers are on this now - appreciate the patience folks! Jerry 2306 (@jerry-2306) · 2025-11-21 · ♥ 1 Any update or ETA on this? Pauline P. Narvas (@pawlean) · 2025-11-21 · ♥ 2 This should be fixed now by the v0 team! Let me know if you have any questions.
