🚨 Firebase App Hosting: Successful Deploy, but Production Still Serving Old Version (Next.js / Firestore / Firebase Studio)

General
1

Hey everyone,

I’m facing a strange issue with Firebase App Hosting + Next.js and would love to know if anyone here has experienced this or found a solution.

Context:

I’m hosting a Next.js project (currently on Next 15.3.3, Node.js 22.16.0) on Firebase App Hosting, with the entire build process handled through Firebase Studio (Firestore + Hosting Console).

On my latest deploy, I pushed version 1.7.0 of the application.
The build process completed without errors, and the Docker image push also finished successfully with a confirmed digest.

Partial Build Log (proof):

> nextn@1.7.0 build
> next build
▲ Next.js 15.3.3
✓ Compiled successfully in 75s
...
digest: sha256:dd6d71904328...
Successfully built image 'us-central1-docker.pkg.dev/imobiflow-96ie9/firebaseapphosting-images/studio:a-utuff7c4m9ib'

The issue:

Even though the 1.7.0 build completed, when I access the production site, the footer still shows the old version (1.6.0).

I’ve already:

:white_check_mark: Cleared browser cache
:white_check_mark: Tested in incognito mode
:white_check_mark: Double-checked on Firebase Console that the build finished successfully
:white_check_mark: Confirmed that the version number in the code was correctly updated before the build

My current suspicions:

  • Possibly a Health Check failure after deploy, causing Firebase to keep serving the old version.
  • Maybe some internal cache (Cloud CDN, App Hosting Cache) still serving the previous build.
  • Or, perhaps, an issue with the auto-promotion of the new image to production, even though the deploy steps ended without errors.

My questions for the community:

  1. Has anyone else faced this with Firebase App Hosting and Next.js?
  2. Is there a way to manually force the promotion of the deployed image, even after a successful build?
  3. Where in the Firebase Console or via CLI can I confirm the actual active production version?
  4. Is there a place where I can check the Health Check history for recent deploys?

I’m happy to share more parts of the log or deployment info if needed.

Thanks in advance for any help!

2

Is the build log showing the name of the commit where you updated to 17? I.e did you really commit and sync properly?

3

So, I made it visually in the footer of the side menu to show the current version. The Studio version is 1.7.1 and the deploy version is 1.6.0.

4

I suspect I’m experiencing something similar; I don’t know the technical part, but there are blocks in the app that do not update while others do. It’s not the browser cache or the CDN; I’ve been experiencing the same issue for weeks. It also depends on the nature of the change being applied. Sometimes I’ve even gone so far as to remove an entire functionality to implement it again and make it work; sometimes it helped, while other times the problem persisted.

5

I was able to resolve the issue. First I sent this prompt:

“The site is not reflecting the latest code changes. Can you add debugging to the build or hot reload process to help identify where the sync is breaking? Also, it would be helpful to include some visual indicators in the UI to show when a rebuild or update occurs.”

Then when completed, I pushed a new deploy and as expected the deploy failed. I sent the error to AI and it was able to resolve it. In a few minutes I was able to resolve a weeks-old issue as well… I hope it can help you too

2 Likes
6

I’m with the same problem, I already spent two weeks in this problem, I’ll try your suggestion and let you know if will work. Thanks

7

For me didn’t work :frowning:
Someone have any other idea?
thanks

8

Only to share with all, my problem was in google app hosting, I change to Vercel and my application worked perfectly.
thanks

9

@Matheus_Nattan @diteixeira89 @Roberto I’d like to learn more about your experiences with deployment. I’ll send you each a direct message.