interestingly, it works properly on the v0 iOS app
Previews are rarely working here. Why? I took a week off from V0 but previews were working in late Jan before I left. Now I can basically only see app when published. The preview has worked a few times (maybe 10-20%?) on new apps but I just gave up building after it kept failing. Canât pin down what makes it fail/succeed.
We canât seriously have to publish our app for every iteration just to check editsâŚ..
This is unusableâŚ..
Whatâs status?
1 Like
Hi I posted the original post, after discussing with V0 support engineer I learned this is meant to happen and not a bug 
with the new visual studio code preview and authentication library detection.
Here is everything I lost since I have to now open a new tab:
- Log dated is not easily accessible by the V0 chat, my development speed has gone down due to this, and from a V0 business perspective, my usage of V0 credits has also gone down.
- Major hallucinations now, I think because of the lack of more data that is lost, since I am in a new tab, the output is just bad. Going directly to Claude has been way better
- More user behavior:
- The constant need to open a new tab to test (to be honest, I didnât care if I had to sign in every time to test my app)
- Dragging images and files in the new tab chat box is not that great, I have to constantly click the + but normally I just drag and drop things in when I had the chat + preview
Ideal path:
- V0 can open my new builds (with authentication still active)
- V0 can see my log data and V0 can use the logs to test and add better reasoning
Next steps:
- I have slowly been migrating to Claude code now (I still love V0 but until this is fixed and previews can be used again, I have no choice but to find other tools)
Feel free to reach out, I want V0 to be my ideal spot, but right now I am not happy with the new updates (other than github branches, that has been AWESOME! If I have another dev branch off of me) but everything that has caused made the whole app not as usable as before. I am sure majority of users are individuals, but I am assuming enterprise customers needed that feature, so makes sense. But solo devs, def can feel the burn it seems from the other post I saw here in the community threads.
3 Likes
Same issue here, had been working for a week in the otherwise excellent UI, with chat on the left and preview on the right, but after I did a PR to wrap the day, V0 instructed me to start fresh with a new branch & new chat the next day. I went ahead, tested, and ran into the dreaded âBrowser Restriction Detectedâ and itâs a complete workflow disaster. Please fix your awesome UI!
1 Like
When I go to the existing chat, everything is gone. No preview, no code editor, No env config, No git. Only chat
This is very critical. I canât even change env variable without wasting credit.
I canât test code without having to deploy to the production
1 Like
Agreed⌠i do know that the v0 team is working overtime to get this all working smooth again! Hang on.
2 Likes
Got preview working on an in-progress project. No idea how.
Started new project, preview doesnât work.
Guys without a preview V0 is entirely unusable. Just revert the update.
2 Likes
Well we are âhanging onâ for almost a month now since that disaster struck. Workflow ruined, apps canât be reasonably developed due to everything @devin-6075 mentioned above.
I think I havenât ever seen a more disastrous out-of-nowhere product update before and I have seen some pretty messed up things. v0 is not some B2C mass-market website guys, it was a fantastic productivity-boosting engine for a lot of people willing to pour in money for what it offered. And you managed to just bring it all down to near-useless form in one update nobody asked for. We really should at least have an option to rollback to previous non-beta approach or to check that we are okay with the auth possibly misbehaving (it never did) for the quick iteration process. We can always check the final state of things at the end using the proposed preview tab.
1 Like
Well i can agree that the auth always worked the way you wanted to work in the old version within the preview, and indeed the new flow makes coding stuff allot slower, 1 thing i personally dont like is the fact you cant copy paste images or just slide images into the chat pop up that also opens when opening a tab. that way i need to save screenshots by hand and then select them with the +. Really slows down the process. But i am 100% sure that the team heard about all our feedback and issues and will come with a fix soon. Last week they already shipped some improvements, lets hope this also gets resolved soon.
Also experiencing this in a brand new project so its even related to legacy projects in the new update
1 Like
here is a broken one for you https://v0.app/chat/kdawgwilk-baker-haven-hj-jRMKhOtIWLB
1 Like
Can you unlist it?
I am having the same issues. I canât do anything and since things are broken I canât get v0 to fix its mistakes.
I canât send the chat link because it has API keys.
My preview environment is just black screen nothing is there.
2 Likes
Oh wow! A ton more people have entered the chat! Hopefully we will hear back soon.
You all must be power users haha probably:
- using supabase for auth
- using stripe
- a ton of new releases going out daily/weekly
Absolutely! It is crazy how many people rely on this stuff, and how threatening it can be to have it go down!
1 Like
OP here, I have posted on X last week and Guillermo sent his team, so I say we hold on until we get an update! https://x.com/toolandtea/status/2021658971501912185?s=20
Yâall can follow me here too on X haha @toolandtea 
1 Like
Appreciate your patience everyone! The team are actively improving this experience 
1 Like
Just so you know for the future, chatlinks are always prive and will not expose any data about your project. Data only gets exposed to people that you gave direct acces to or the v0 team itself 
Cheers
- MarnixB
2 Likes
Shoutout you.
1 Like
Thanks for the X post urgency, it really is as youâve mentioned. The unsettling current state of things made me to go out of my way and sign up for Claude Code already to try it out. As much as Iâd hate to make the switch, because I really loved the previous v0 workflow effectivity, if these things donât get fixed quickly, the move might be final. I really hope the team will pop up with some solution fast.