V0 Not Updating

v0 is responding and updating when we ask question but when i try to manually edit codebase its not asking for save if i do manual save it will not reflect after page refresh.
Is anyone else facing the same issue?

1 Like

Did you know there’s another category dedicated to v0 topics? A human should be here soon to help, but the answer may already be available even faster in one of these other posts.

Our docs are a great place to start.

We also have a walkthrough to help guide your workflow.

And these recordings can give you a look at v0 features and strategies in action shown by our Community:

https://community.vercel.com/tags/c/events/42/v0

I haven’t been able to replicate. Can you share a chat?

1 Like

Most of my projects don’t allow me to save changes after manually editing the codebase.

So I ran two tests:

  1. I asked V0 to create a sample page, then manually edited the code. It gave me the option to save.
  2. This time, I uploaded a project using the “Upload a Project” option (via ZIP). After manually editing the code, it didn’t give me a save option, and if I tried to save manually, the changes were reverted after refreshing the page.

I just figured out one more thing: I can create new files in the project, but I can’t save them after writing anything in them.

Latest Update:
I figured out one more thing: saving only works for TSX projects, not for others like Python, Go, etc.

I’m sharing a sample chat that I created for testing. https://v0.dev/chat/project-hNpLqR4Se6o

This is the same bug here, reported internally

https://community.vercel.com/t/saving-edited-files-wont-work-anymore/10822/2

1 Like

5 posts were merged into an existing topic: Saving edited Files won’t work anymore

Same issue here. And nothing has worked so far including “starting over” with a zip file. It’s as if there’s a setting that somehow stopped the save function without any browser errors. Also upsetting is that I just upgraded my account and yet I’m more stuck than ever before. I hope someone can bring some clarity to this issue really soon. This issue is holding up major progress.

Same here. Having this same issue for the past three days. What is the v0 team doing about this heavy duty bug?