Pauline P. Narvas Hey, @iamalextremo! Have you got any chat examples? It'd help us dig a bit deeper. One thing to check is to make sure you’re not including the .tsx extension in your import: import { useAuth } from '@/lib/auth-context' Let us know how you get on!

Peter Raedschde You are correct - this appears to be a malfunction in v0's ZIP import process. Based on the images you provided, I can see the factual discrepancy: Facts from the images: Import Dialog (second image): Shows proper lib/ subdirectory structure Contains files like lib/utils.ts, lib/errorHandler.ts, lib/neon-db.ts, etc. 855 files were selected for import Generated CodeProject: Files that should be in lib/ are placed at root level utils.ts, errorHandler.ts, neon-db.ts, etc. are missing the lib/ prefix Directory structure has been flattened Open Issues: Directory Structure Loss: The lib/ subdirector

Pauline P. Narvas Hi, @engamin1! From the error you're seeing, it looks like the issue is coming from how the client token is being generated during your upload flow. The “Failed to retrieve the client token” message usually means something’s off in that token generation step that enables uploads from the client side. Here are a few things worth checking: Your API Route Setup Double-check that your /api/upload endpoint is set up to support the client upload process. It should handle generating the token correctly and allow the upload to complete without issues. Environment Variables Make sure the BLOB_READ_WRIT

Eng Amin The error is only occurring in the v0 preview but after deployment the upload is perfect working. So i got this after i published the error Thnks

Pauline P. Narvas Hey, @orkun-4891! Could you share your workflow? And a link to your chat? You should be able to just delete this component in your code though.

Orkun 4891 Hi @pawlean this is the chat link v0.dev/chat/fork-of-v10-myjvkIdRglO

Accounts 2854 Don’t expect a reply they do not like their clients around here.

Jacob Paris This was an issue on our end that affected a small number of users and it should be fixed now, can you try again?

Jacob Paris Can you share a screenshot of what you're seeing?

Jacob Paris The best way to get yourself out of issues like this is to go back to the last version that worked before you started getting the issue click "view" (not restore) and then with that working chat in the preview, click "fork" to spin it off into a fresh chat That'll clear the message history and anything about the issue that could be stuck in the chat context, and then you can send your message again with better luck

Pauline P. Narvas How are you calling them right now? Can you show any examples?

Dancho8 It was very strange, but when I opened the development environment today, the server action that was causing the error was working normally. I thought that the policy for the v0 server action had been updated, so I spent the whole day yesterday converting all server action processing to API Routes... but it turned out that there was no need to do that. (I ended up using up a lot of credits for that( ﾉД)…) Anyway, I don't know what the cause was, but it has been restored. However, if something like this happens again in the future, it will be a big problem. When building server-side logic, I pr

Jacob Paris If an AI model implements a feature for you with errors, and one bug fix attempt doesn't work, I usually roll back and ask for the feature again. That stops the codebase from getting worse through dozens of partial fixes, as well as muddying up the chat context with debugging info rather than product info If it still doesn't work after the second attempt, try breaking it down into smaller features. For example, if you're building an image upload system, ask for just the UI in one message and then have it upload to Vercel Blob in a second message. You can chat with v0 to get ideas on how to bre

Jacob Paris The version selector has been moved here

Jacob Paris This appears to be a bug in v0's git sync that allowed syncing files that are above v0's file size limits. I've passed this on internally so we can prevent this from happening In the meantime the fastest fix would be to remove the large files from your codebase if it's code, break into multiple files if they're assets, you might need to move them out of source. Vercel Blob makes it pretty easy to upload and reference assets for your project

Itesainnovation Hey! We have the exact same issue, were you able to solve it?

Fabrizio I just gave up on v0 and asking for refund... yeah

Amy Egan What reset date and time does it show now? Can you post a screenshot?

Amy Egan I don't see a v0 Premium invoice associated with the account you're using here. Do you have a different account the you upgraded?

Anshuman Bhardwaj Hi @8372841-9192, I'm sorry that you faced this issue. Did you try the @ tagging file feature to target specific files?

Pauline P. Narvas Hey, Peter! Welcome to the Vercel Community. Are you still seeing this when you try to upgrade now? It sounds like you may have hit a limit, which can happen if there are multiple failed payment attempts. For now, could you try clearing your browser cache and cookies and maybe try a different browser or incognito mode when upgrading? Thank you!

Amy Egan I posted some quick tips in community.vercel.com/t/all-my-recent-changes-are-consistently-breaking-my-webapp/15473/8 But you should check out Jacob's recent post for some of the best advice! community.vercel.com/t/improve-v0-quality-with-strategic-forking/16487

Pauline P. Narvas Appreciate the feedback, Kevin. Thank you for sharing! We'll get this over to the v0 team as we continue to improve our product.

Pauline P. Narvas Hey, Kevin! Can you share what your prompt was, and output? It'd be helpful for us to debug what went wrong here. We'll also share this feedback with the v0 team. 😃