Bug: Ionic serve showing old content

[matheusdavidson]

Short description of the problem:
Ionic serve/livereload displays old content after refreshing. When I make changes to my app, the build completes and browser refreshes, then I see old content. Sometimes the changes do not apply, and sometimes I see an old page that I already changed multiple times.

What I do to resolve this is restart ionic serve or run npm run build and refresh the page manually. Clearing browser cache and refreshing page solves this issue some times, but not all the time. So I don't think it's a browser cache issue.

What behavior are you expecting?
When the browser refreshes after a new build, it should display new updates.

Steps to reproduce:
This issue is really random.

Create new project
Run ionic serve or ionic run -l
Keep making changes to your app
Eventually the problem will occur

Which version are you using?
3.1.9

[matheusdavidson]

not fixed as stated in #825

[jwelmac]

I am having the same problem

[jmarceli]

Did you try to check "Update on reload" in Google Chrome Dev Tools (inside Application tab):

This solves my issues instantly...

[physedo]

same problem here

[realtrehan]

This is really very annoying..the caching of pages. Is there an option to force not cache anything while in dev debug mode? I tried the dev tools in chrome but still shows cached page code. Any update to fix this ? A serious productivity killer as you are struggling to debug issues (which are complicated coz of caching pages views)

[windwp]

same problem here

[smartin85]

same problem here. It´s not a browser caching problem. The content in www-folder doesn´t update.

[rmfranciacastillo]

Can't believe that this problem persists since 2017 and ionic 2. It's really frustrating updating components this way. Anybody knows if there's a cli command to avoid caching.

[swvcc]

Having the same problem. This is a petty issue and should be resolved. There is no reason caching should be out of control like this.

[matheusdavidson]

anyone having this issue, use ionic 4 if you can, it doesn't use app scripts anymore so the problem will go away

[swvcc]

using ionic 4 is not a solution. I've been explicitly told in the Ionic support channel by engineers that Ionic 4 is not ready and was told not to use it. This should be fixed in the meantime.

[matheusdavidson]

@swvcc i created this issue because another one with the same bug was here for 2 years and it was closed, do you think anyone will solve this? haha

I'm using ionic 4 for some time now and today they released a beta, use it, don't worry, its just angular.

[Ketec]

Same issue - sometimes i may not instantly notice that it server old, cached version and i end up tryign to debug the problem - wasting time.

So i have to shut down the serve and restart.

Just moments ago it server hours old version of the code - code i had changed and already commited to git.

Ionic 4 is not a solution indeed - it is in very early development and is not fit for commercial production.
And likely won't be for another year. And even then migrating over is likely going to need huge amount of work.

[pivalig]

Try to look at the service worker approach