Is the paid subscription as buggy as free version?

v0
1

I had started using v0.dev since the beginning of this week.

Initially it was doing well, but since yesterday it is messing up code with generating arbitrary code, trying to fix existing files repeatedly and messing existing code.

Since there are 3 messages available daily, all get consumed in Continue Generation, as the original task from 2 days ago is yet to be finished. I suspect it may be due to lower resources allocated to free plan, as I’m getting a lot of the following in the generated files:

... This file was left out for brevity. Assume it is correct and does not need any modifications. ...

// This problem is impossible to solve without the original code. The updates section indicates that several variables are undeclared, but without the original code, it's impossible to determine where these variables are used, what their intended purpose is, and therefore how to fix the undeclared variable errors. I cannot add imports or declarations without knowing the context.

and

// I will assume the loading.tsx file is attempting to use variables without proper declaration or import.
// Without the original code, I can only provide a placeholder that addresses the errors by declaring the variables.
// A proper solution would require the original code to determine the correct import or initialization.

const brevity = null; // Placeholder declaration
const it = null; // Placeholder declaration
const is = null; // Placeholder declaration
const correct = null; // Placeholder declaration
const and = null; // Placeholder declaration

function Loading() {
  return (
    <div>
      <p>Loading video...</p>
      {/* You would likely have more complex loading UI here, potentially using the declared variables */}
      {/* Example usage (replace with actual logic): */}
      {brevity && <p>Brevity: {brevity}</p>}
      {it && <p>It: {it}</p>}
      {is && <p>Is: {is}</p>}
      {correct && <p>Correct: {correct}</p>}
      {and && <p>And: {and}</p>}
    </div>
  );
}

export default Loading;

This is in addition to the page being unresponsive every few minutes irrespective of the browser.

Are the things any better with premium plans? I’m worried as I don’t see any direct support options listed either.

1 Like
2

Did you know about these other v0 resources? A human should be here soon to help, but the answer may already be available even faster in one of these other posts.

This guide is a great place to start.

And these recordings can give you a look at v0 features and strategies in action: Topics tagged v0

3

It’s notorious for creating fallback options. So for each new chat/fork, I give mandates:

  1. Code Quality Standards:

  2. All scripts must have comprehensive comments explaining purpose, functionality, and usage

  3. Implement robust error logging for all operations especially when calling out functions

  4. Use try/catch blocks with specific error messages for different failure scenarios

  5. Ensure graceful degradation when non-critical features fail

  6. Provide an analysis/understanding of new requirements first before implementing them.
    I then give it the instructions.

  7. Data Integrity:

  8. Never implement fallback or alternative data for testing without explicit approval

  9. Suggest options when needed but wait for my decision before implementation

  10. Maintain strict separation between production and test data

  11. When in doubt about a UI/UX change, clarify first before implementing

Problem doesn’t go away with PRO. Gotta teach it how you want it to respond to you.

Caveat: This is NOT fool-proof but it helps reduce the number of incidences and my frustration.

3 Likes
4

sometimes it does due to AI models being hallucinating. Maybe you can try it on Chrome since I too sometimes face this issue, but after a quick refresh it goes back to normal.