I’m facing a serious issue where I can’t preview my project at all — not in the latest version, and not even in very early versions (including Version 1). I currently have over 144 versions saved.
I’ve spent a lot of tokens trying to fix this through the engine, but the same problem keeps happening. The engine keeps running, saying the issue is solved, but when I check the preview, it’s still broken. I’ve repeated this process many times with no success.
The only explanation I can think of is that I bulk-deleted more than 10 messages from my code history because they all had errors. I didn’t delete them one by one — I deleted them starting from an earlier message higher up, which removed a whole block of messages at once.
I’m wondering if this bulk deletion might have corrupted something in the project history that’s preventing any version from compiling or previewing now.
Could you please investigate this and let me know if there’s a fix? I’ve invested a lot of time and tokens into this project, and I really need to get the preview working again.
And yes, I’ve also tried creating a fresh fork — with both old versions and new versions. Unfortunately, I still see the exact same issue: the preview doesn’t work in any of them.
Regarding integrations — they’re just some basic ones like Stripe, keys, etc. Nothing critical at this stage, so I don’t think they are the cause of the issue.
One thing I believe might be a core problem: at some point, I was connected to Supabase, but then I released all of the Supabase data. After that, I only wanted to keep the UI and design (the front-end), without the database. I’m not sure what happened after that change, but I think this could be one of the reasons why the previews completely stopped working.
After this conversation, I think I may have identified the core issue — though I’m not 100% sure. At one point, I only wanted to keep the UI and design, so after I finished the whole front-end, I migrated to another back-end tool. To do this, I went into the integrations and deleted all of the Supabase database. I believe that action might be a root cause of the current issue.
The other possible factor is when I bulk-deleted multiple messages in the chat history (instead of one by one). Between the Supabase wipe and the bulk deletions, something may have broken in the project.
However, after reading the forum, I’ve noticed a lot of people are experiencing the same issue I am, so I’m not sure if what I did is directly the problem or if it’s a broader bug. That’s also why I created another post — not to spam, but to gather everyone’s reports in one place so you and the team can respond once and others can see the solution.
That’s where my head is at regarding what might be happening.
Thank you for confirming and for escalating this to the v0 team. That’s a relief to know it’s not just me, and that you also hit the same syntax error.
I really appreciate you taking this forward. Please keep me posted as soon as you hear back — this issue is completely blocking my work right now, so any update will help a lot.
Yeah, exactly — that’s the reason why I created that post. It wasn’t to spam at all. I read through the forum and saw at least five or six people having the exact same issue, so I thought it would be more useful to gather everything in one place. In that post I summarized the whole problem, so if you and the team answer there, everyone can see the solution instead of you having to answer each person one by one. I really respect the community, and my intention was only to make things easier for everyone.
One thing that may help the team: from what I’ve observed, the agent’s debugging logic seems to only focus on the latest visible issue instead of doing a full analysis. So it patches the first error it finds, says “fixed,” but doesn’t go deeper to the core problem. That’s why people (including me) end up spending a lot of tokens — it keeps debugging symptoms, not the root cause. The agent is great overall and definitely helpful, but this part of its logic feels limited.
Hopefully this feedback helps the team while they investigate.
Thanks for sharing the prompt solution. I tried it, but unfortunately it didn’t work I’m still seeing the exact same problem with the preview. The same error keeps coming up
It’s now been over 3–4 days since I first reported this issue, and it still isn’t solved. I saw that you marked it as resolved for someone else, but for me the exact same problem is still happening.
What’s going on here? Why is this being marked solved when the issue clearly persists? I’ve been completely blocked for days, unable to preview any version, and I’ve already spent all my tokens trying to fix this problem through the agent with no success.
Because of this, I think it’s only fair that my $20 subscription be refunded — I paid for a working service and support, and right now I can’t use the product at all. Please escalate this to your team so both the technical issue and my refund can be handled properly.
I know there’s multiple threads around, but did you manage to create a new fork and prompt there? The issue for this was related to the file extensions as I shared in the other thread.
You can request a refund in vercel.com/help - please do so and link back to this conversation.
I’ve forked your chat and trying to do it myself right now. Will let you know what happens!
