Skip to content
Get a quote

Firebase Hosting problem

Why does my Firebase site still show the old version after I deploy?

The deploy finished without errors, you open the site, and the old version is still there. Customers see yesterday’s prices or the bug you just fixed. Firebase Hosting serves whatever was deployed to the live channel of that site, so the question is where the new version went, or what is still holding the old one. Here’s what the docs say, in their words, or hand it over at a fixed price.

Rather hand it over? App Fix Ticket: One reproducible bug in an existing mobile or web app, diagnosed and fixed.

Pay $450 for a DiagnosisAsk a question first

Full refund if Simon can’t take it on once he sees your project, or if you cancel before work starts. Refund terms.

Short answer

Open Hosting in the Firebase console and check the Release history for the site your domain uses. If the latest release isn’t there, the deploy went to a preview channel, another site or another project. If it is there, check that the build ran before the deploy and that firebase.json deploys the build folder, then look for an old service worker or long browser cache headers.

Rather not fix it yourself? App Fix Ticket starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.

Why the old version still shows, and the fix

  1. 01

    It went to a preview channel, not live

    “After you deploy to a preview channel, Firebase serves your web app at a "preview URL", which is a sharable, temporary URL.” Firebase, Test and share changes before going live

    A deploy to a preview channel gets its own temporary address and leaves the live site as it was. Deploy to the live channel when the changes are ready.

  2. 02

    It went to another site or another project

    “Each site hosts its own collection of content.” Firebase, Share project resources across multiple sites

    One Firebase project can hold several Hosting sites, and the command line deploys to the project it is set to use. Check which project and site the deploy reported, and which site your domain is connected to.

  3. 03

    The old build folder was deployed

    “The public attribute specifies which directory to deploy to Firebase Hosting.” Firebase, Configure Hosting behavior

    Firebase deploys the folder named in firebase.json as it is. If the build didn’t run first, or firebase.json points at a different folder than the one the build writes to, the old files go out again.

  4. 04

    An old service worker is serving cached files

    “refreshing the page isn't enough to let the new version take over.” web.dev, The service worker lifecycle

    Sites built as a PWA install a service worker that can keep serving the old version. By default, a new one waits until every tab using the old one is closed. If the site updates for new visitors but not for you, this is a likely cause.

  5. 05

    The browser is holding files because of long cache headers

    “If you redeploy your site's content, Firebase Hosting automatically clears all your cached content across the CDN until the next request.” Firebase, Manage cache behavior

    Firebase clears its own CDN cache on every deploy. If visitors still get old files, look at the headers in firebase.json: a long Cache-Control on HTML or on files without a version in their name lets browsers keep using them.

Checked against the vendor’s docs on : Firebase docs: Test and share changes before going live; Firebase docs: Share project resources across multiple sites; Firebase docs: Configure Hosting behavior; Firebase docs: Manage cache behavior; Firebase docs: Manage live and preview channels, releases, and versions; web.dev: The service worker lifecycle.

Rather hand it over?

Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.

“Very responsive, attentive to fixing bugs, and completed the project as needed! Thank you!”
A buyer in the United States, July 2022. Shopify on Fiverr
All 127 Fiverr reviews

Related: Firebase Hosting Page Not Found after deploy · Lovable app blank page after publish · Vercel 404 Not Found after a ready deployment · Supabase app slow

Questions

More on this error

How do I see what is live right now?

In your Firebase project’s Hosting dashboard, the Release history table lists the releases of the live channel that Firebase has kept. Each deploy creates a release that points to a specific version of your files.

Can I go back to the previous version?

Yes. In the Release history table, hover over the release you want and roll back to it. Rolling back creates a new release that serves the same content as the earlier one.

Why does it look right in a private window but not in my browser?

A private window starts with no saved cache and no service worker. If the new version shows there, the old one is being held by your browser’s cache or a service worker rather than by Firebase.

Can you fix it for me?

If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.

A different error?

Describe it and get a written quote

Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.

Describe your problem All fixes