Starting this thread to collect cases where the v0 preview works, but the site looks different or breaks when deployed to Vercel.
If you have encountered this, please reply with a chat URL or ID (the numbers/letters at the end of the URL). You do not need to make your chat public.
If you can share the deployment URL, that can help us find project info more quickly. Supporting screenshots are also appreciated
Seeing a pattern where v0 previews look fine, but live Vercel deployments initiated via v0 result in broken CSS/layouts, even when deploying previously stable code. This points to a potential v0 build/deployment pipeline issue that might be affecting multiple users.
Perhaps Vercel should take a look?
Thanks @shihpakhung-7440. We had all of these reports individually, but I appreciate you recognizing the pattern and listing them together. I opened a new thread to collect related reports and moved your post here.
Please post more links here if you see other cases of this
is it only me having the issue that code changes are not neither affecting the preview nor the deployment??? Is the hep experience with Vercel this horrible? how is actually helping?
Can you share screenshots to show us what you see?
No changes either manual or by the ai are being rendered in the preview nor deployed when deploying. The code is there and changed and nothing is happening.
here is my site in preview mode
I tried to add v0 to fix, but affter v0 fixed i still see the grey color in prview mode not the same in production mode. it’s weird.
In my case, the issue was caused by the way globals.css was being imported. The exported code was using:
import "./globals.css";
However, I think it should be:
import "./../styles/globals.css";
I had two different globals.css files, and the incorrect one was being imported. After correcting the import path to point to the right file, everything worked perfectly.
Thanks for sharing this solution, @sizandyola.
Everyone else, do your projects also have extra globals.css files that may require a modified import?
Hi @amyegan I’ve had several versions and never had any disparity between preview and published version until now.
After making a simple text change, the formatting of the entire page (text and graphics) is messed up. What are the options to resolve this? Thanks!
https://v0.app/chat/voyager-ai-landing-page-naqLXqbKB6H#hHwgRGlFPa60QO7rgTDQK94KSe9qpU35
Oh no! I thought this was fixed. Hadn’t seen it happen for a while.
Thanks for sharing the chat. I remixed a copy on my own account and deployed, but the site and preview look the same to me. Can you send screenshots to show what doesn’t match?
v0 Preview
Published site
Thanks Amy. Here is what the production site and preview looks like. I tried to reverting to previous version but even that doesn’t help. We are launching soon and this is a blocker.
Interesting. It looks like most of the CSS isn’t loading on yours, but it worked fine when I deployed my copy of the chat you shared. Do you see any errors in the dev tools console when you open the deployed site? What happens if you duplicate the project and deploy from the copy?
property-listing-portal-rm9yUvF6q4S
code and file inside the v0 ide but it’s not getting to github or vercel on publish
Here’s what I saw when I visited the site just now:
It starts with the text over a black screen and shifts into some film scenes. That feels like the intended experience, but let me know if there’s something wrong with that.
Since it’s working for me, I suspect that either you’ve found a solution or there is something preventing the styles from loading for you. Do you see any errors in the browser console or network tools?
Yeah so i managed to fix it after a lot of iterations later. Very frustrating that i had to buy a subscription just to get my site working properly and reverting back to old codes didnt work either.
This is what V0 says the issue was:
The issue was a combination of:
generateBuildId function forced a completely fresh build, bypassing all cached artifactsAppreciate you coming back to share what was causing the problem and how you fixed it. This is really good to know