Beyond frustrated

I can quantify in actual dollars, thanks to this platform, how much I have spent and how many times*** the conversation spirals around “IT’S STILL THERE. Line 230 still has || "/placeholder."

Which of course is confidently “fixed” at the end of the work with “I’ve removed the || "/placeholder.svg" fallback from line 230 by rewriting the entire..”

I have spent two hours TODAY at least, with V0 spinning its wheels on the same fix.* * * It was 20 distinct code generations, and $20, on top of the wasted funds from the outage two days ago. I hate that this is so useful, but also so incredibly flawed.

Vercel Staff

Sounds like a problem we'll need to look into. I'll let the team know. As a quick workaround you could open the code editor, remove that bit of code from line 230, and save your changes.

Keep in mind that the "Fix with v0" button shouldn't use any of your credits. If it does, please share the chat ID so I can flag that with the team as well

https://x.com/v0/status/1973517338709467622

Vv0 (@v0)

It no longer costs credits to use “Fix with v0” when v0 makes an error.

1.6K likes · 58 reposts · 143 replies · 173.6K views

Thank you for the reply Amy, and for forwarding the information to the team. I am appreciative that button does not use credits, however it also allows no additional text or context to be added, and when spinning wheels as I have been, the button gives no way to prompt V0 in a way to somehow get out of that cycle.

Vercel Staff

If you're still stuck on this, would you be able to tell me the chat ID? That'll help us find the logs related to this issue.

This topic is closed. It no longer accepts new replies.