Just got the new Git branch method for v0 but now that it is implimented, my code no longer previews (literally changed nothing, just did a new branch as is now required). The message is:
What’s the fix?
My private chat is: https://v0.app/chat/sungkhum-translator-toolkit-live-jLtYQJHet0o
This one still previews: https://v0.app/chat/3-duplicate-of-fork-of-translator-toolkit-3HdxNUFp5UA (but I can’t do any more chats there because it requires that I make a new branch).
I ended up chatting in the chat with the broken preview and that seems to have fixed it somehow. Poor user experience though, hopfully will be fixed soon.
Does it every time I have to create a new branch though. Super annoying and makes me waste credits because I have to chat before I can preview.
And now my latest branch is changing the code, but the “Publish” button is disabled because it thinks there weren’t any changes to the branch (there were, I just did the pull request and merge manually in github).
Not super happy.
Also, more feedback on the new “merge” workflow. I hate the naming of the chats beacuse I have no idea what they are for - they are named after what I was doing, but they don’t have a name of the actual chat or project. So it makes it hard when I am working on multiple things at once. Bad UX.
The bug where code has been changed but I can’t push is still happening as well (showing there are changes in the background by showing the diff view):
Im in the same boat. Changes are pushed. it doenst detect deploynet errors like multiple dynamic url slugs. It cost me 4 hours of headaches and $125 in tokens.. this new git shit is bad and wasting time. How can we go back to the old publish method. I like when i can choose when to create a new branch and not require it on all publsih
Now I’m getting this instead of a preview:
I used to be able to preview fine. So I don’t really like this new direction (fine to warn me, but if it works, why prevent it).
The new merge feature is better now - as long as the chat
But I hate I can’t preview and have to open a stupid window (and can’t view code when I do) even though I could before:
Thank gosh I’m not the only one. Thought I was going insane! Ended up deleting branches, regressing back in code because of this.. preview is completely broken when auth is involved. Iframe policies, sandbox, this beta feature has the potential to be great, but for forced “Improvements” like this, regression should be supported at least temporarily until the system is stable. This is breaking production currently. Their needs to be a way to either opt out of the beta OR fix the auth restrictions.
The Github change is better, but why remove the ability to “Disable auto commit” and push? This was a critical feature. I don’t want EVERY change being pushed automatically with HIIT. It’s important code is reviewed manually, especially for production-grade products.
Vercel, please address this ASAP. Thank you.
My preview is back this morning!
Thank you for the detailed post! Flagging to the v0 team.
