its fails to deploy
I dont know how to reproduce, its just fails on every code version that was working 10/10 so far
I cant share publicly project URL/INFO. I am deploying the built with v0, that was working and all previous 20+ versions. I tested all of them, none is working suddenly and can’t be deployed.
here is the screenshot
I need to deploy my code to production, its critical for me to be on time, but its failing no matter what version I try.
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:
Hi @shtefcs, sorry that you are facing this issue. Without looking at the code/chat, I can only recommend creating a fork of the chat and deploying to a new Vercel project instead.
If you need more help, please share the chat ID with us. You can keep the chat private.
Brother, thanks for the quick response. I did forked however still under the same project, and its not working.
Here is my forked version, please try it https://v0.dev/chat/fork-of-fork-can-devs-do-something-sse-parsing-is-RSizCbXmX6p
Thanks. Have you tried un-linking the Vercel project in the fork and adding a new Vercel project to it for testing?
this is happening for me as well - you might need to check if its affecting multiple users… been trouble shooting for 2 hours now
Hi Harry, thanks for sharing this. Let me share this on priority with our team. Can you share your chat ID?
that and like all my previous builds - successful deploys would redeploy with the same error - nil changes on my end
Yes, I’m aware of that, but this is really strange. The /api/bots/create-user route is something I worked on 5–7 days ago, and we haven’t touched it since. I wouldn’t reach out for support if I believed the issue was in my code—I genuinely think the problem lies in the deployment.
Let’s think through this logically and draw some conclusions.
First, as I mentioned, I haven’t worked on that part of the code for over a week, and I’ve deployed the app over 100 times since then—literally—without encountering this error or anything similar.
Second—and even more important—I was able to deploy version v48 (just as an example) without any issues. But starting around version v54, I began running into this error. Naturally, I suspected it was related to some recent changes in the code. So I checked everything thoroughly, even redid parts, but nothing pointed to that route or anything related.
I tried again—it still didn’t work.
So I thought: let me go back to the last version that worked—v48.
Guess what? That version, and even ones before it, now fail too.
So the logical conclusion in my mind is that something has changed on Vercel’s build side. It’s now starting to flag or complain about the /api/bots/create-user route—even though it’s been there untouched for over a week.
No bro I didn’t, that would mean I need to add so much things, DB, ENV var, etc. It would be painful.
I thik thing the issue is on Vercel side honestly, if you just follow my previous response, logically you would conclude there is something strange happening suddenly with Vercel deployment.
yeah its gotta be vercel side - i am experiencing the same thing.
visually on my site looks absolutely cooked now for some reason.
but i am running the entire site and functions through the preview without any errors - apis and everything. Chatgpt told me it was something to do with a new update on next js and vercel that means its stricter? I dunno… but yeah
Update: I’ve forwarded this issue to our v0 team and I’ll keep you posted when we have updates. We are sorry that you’re facing this issue.
Thank you Anshuman! Anyway you can mark as priority, since I am stuck for last 6 hours and I need to deploy fix to the production!
@anshumanb since I shared my chat with you on private, do you have access to my ENV and API keys? Can u see it?
Hi @shtefcs, no. We can’t see your environment variables. Your information is safe and secure.
Thanks! Any update man? I know I am boring, but this is reaching critical point, I need to push fix on web app and I can’t for last ~8 hours.
Has this been resolved and can we get a refund on all prompts please? Thanks
Brother, the deployment was working after 12 hour of waiting, and not response from Vercel team.
then it worked for few hours, and now its again stopped working.
I noticed then the Nextjs version is changed to v14, it fails to deploy. But when the version is v15 it works okay. Why the version is changed and do we fix this?
