Redeploy Not Updating Live App on Emergent – Possible Cache Issue

[peak cove]

Hi everyone,

Sharing a deployment-related issue in case it helps others or someone has faced the same.

In my Emergent project:

The app was already live

Updates save correctly in the project/editor

When I click Redeploy, deployment completes successfully

But the live app does not reflect any of the new changes

It keeps running the old version

There are no build errors, which makes it confusing. It feels like the redeploy might be:

Reusing the old container

Pulling from a cached build

Or not invalidating the previous deployment session

If anyone has faced this or knows:

How to force a clean rebuild

How to ensure redeploy actually picks up latest changes

Please share your insights. This could be helpful for others too.

Thanks in advance.

[quaint swan]

There are two cases when you generally see this behaviour. One is that you check your deployed app right after deployment. Give it a minute or two and do a hard refresh using CTRL+SHIFT+R. This will show you the new version most of the time.
The other one is that if the updates you are missing are related to the database, they will not show. Emergent has separate databases for preview and deployment, which is a common practice to separate test data from production. If it is content, then you will have to add or modify it from the admin panel on your app (have the agent make it if not already done) in your deployed app.

If both of these do not fix your issue, then raise your issue with [email protected]

[topaz wedge]

facing same issue how did u solve it ? please it is urgent

[lofty whale]

try this

Cache-Busting Mechanism Explanation

What it would do:

When users visit the auth page, their browser might cache the JavaScript bundle or the API response for registration-status. This means even if you enable open registration on the server, users could see the old cached version that still requires an invite code.

A cache-busting mechanism would:

1. Add a timestamp to the API call - Force the browser to fetch fresh data: /api/auth/registration-status?t=1234567890
2. Add cache-control headers - Tell the browser not to cache the registration status response
3. Force re-fetch on page focus - When user returns to the tab, re-check registration status

This ensures users always see the current registration settings, not cached old ones.

ask ya bot to see if this would work

[sudden gorge]

facing same issue😓

[topaz wedge]

it is a pain it happeend to me after many sucessfully deployements: in my case AI agent was advising to contact the physichal support, unsuccesfully. So I took the decision to revert to a stable older version loosing all the work done in between (lot and expensive) . I wrote customer support to investigate why this happened, find solutions because i now fear that it may happened again

[crude oak]

ive had this, it wasnt passing over the new files in preview to deploy, tell it to!