I already added the database URL as SUPABASE_URL, but it’s not clear which variable I should use.
This is probably a bug: when I try to start a new chat from an earlier version, it creates a new chat that includes all the changes I made after that version. In this case, using v1 still includes all later changes in the new chat.
The same issue has recently affected all projects that received the last update, wasting time and tokens. No matter what I try, I keep getting this consistent error in both PREVIEW AND LIVE DEPLOYED PROJECTS: Browser Restriction Detected. It finds authentication libraries in the generated code that might not work as expected in the embedded preview due to browser restrictions. To view the preview, open it in a new tab. None of the solutions I tried have worked.
I simply can’t ship.
Since the beta rolled out, my build productivity has dropped to 5% due to:
Thanks for the info @ryanb-hamedia! I’ll raise this with the team.
Hey team,
I’m seeing some heavy friction in the latest v0 iteration. I use this tool to ship at high velocity, but a few core infra issues are currently killing the “flow state”:
Preview (Still Broken): The preview is failing to initialize even on fresh projects (ruling out auth/session lag). It’s making the “prompt-to-view” loop impossible. No design mode.
No Manual Preview Build: We need a manual “Build Preview” trigger—just like we had. Currently, there’s no way to sync manual code tweaks without opening a PR and then asking the AI to “re-edit” the file just to trigger a build. It’s a massive time tax.
Unreliable Checkpoints: Forking or starting from a specific checkpoint is currently non-deterministic. I’m seeing leaks where changes from later checkpoints bleed into earlier ones. Last week, I had to drop into a Git Desktop terminal just to perform a clean rollback. That’s the antithesis of the smooth, “it just works” experience v0 is known for.
Love the tool, but the infra is making it super hard to ship. Any updates on a fix?
I am having this same issue and the same error message. It seems to having authentication issues with the database.
Can you share a chat link? Thank you!
Flagged to the team!
There are so many issues with the latest V0 update that messed up my current prototype build, and I am at a stopping point. I copied the chat or even created a new chat and copied my repo, but still seeing the issue. I prefer the previous V0. Can I downgrade?
I might use switch to Base44 to continue working on my prototype
Same issues that everyone else is seeing
Sorry to hear this, Andrew. I’ve shared it with the team!
If you have chat links handy that would be fantastic.
Fire your product management team, whoever making users life complicated. All these latest releases are useless and I may move to other platforms with all my 18 projects. First Git branching and now this stupid error.
Browser Restriction Detected
Found authentication libraries used in the generated code, which might not work as expected in the embedded preview due to browser restrictions. To see the preview, open in a new tab.
As you can see ladies and gentlemen, this is the result of pressurised incentive to push out “game-changing” updates without thorough testing which results in a complete breakage for every single loyal and paying customers, completely diminishing ease of use, stability-and driving customers away from this platform.
Please fix this, it’s been weeks now. I’m having to use Codex in the mean time, whilst V0 is still charging me-for credits which I can’t use in any manner which is suitable.
When you open in a new tab, are you still seeing this?
How is v0 charging you credits when you’re not using it?
Re-read what I stated, I said I’m still being charged for credits which I can’t use. Credits are included in the subscription, I’m being charged for a subscription which is currently unusable in the current state of V0. That is my point. Hope it’s fixed soon. As long as the credits are rolled over I don’t mind, I’m currently using Opus 4.6 and Codex with VS studio in the mean time.
Heard, shared with the team 
Thanks!
I wouldn’t suggest this. You’ll burn through credits and the issue will persist
Obviously it wouldn’t show in a new tab preview, but as mentioned above, that is not a usable workaround:
Interestingly enough, the exact chat somehow randomly launched the embedded preview after a refresh ONCE today (so it can actually run!), but fails to do so constantly otherwise.
It’s been two weeks since the last update and introduction of this horrible new builder experience-breaking workflow, which happened without any warning whatsoever and we still don’t have a fix for it. Why did you have to break a perfectly working smooth product and WHEN are we getting the much needed fix?
The v0 team shipped fixes yesterday, and are continuing to. Appreciate your patience!
@pawlean I suspect this is a Supabase-related issue, as it happens EVEN on new projects/chats.
Here’s a new chat where it occurs. All my current and future projects are on Supabase.
Whenever using auth in your projects you will be asked to open a new tab to be 100% sure that the auth works the way you want it to work. The team is working on getting the designfeature working again in these cases and i hope they will also fix the logging/fix for free options within this new tab. but nothing we can really do about it for now.
