Browser cache issue after any change in the UI

[vishalkumar1305]

Hi experts,

I have made a custom SAP UI5 application in HCP. I am facing the browser cache issue in the application. Whenever I am doing any change in UI the changes are not reflected in the application. I need to do hard or empty cache reload to see the changes.

I am directly loading the component.js(not using index.html) file to load the application so I can't use the cache buster code(which is handling cache buster issue automatically) which we write in index.html to handle cache issue.

[former_member365727]

check if this link helps

[vishalkumar1305]

Yes this link have the cache buster code but that can only be written in index.html but I have already mentioned that I am not using index file to load the application. I am directly using component.js to load the application.

[former_member365727]

As there is no 'index.html' file, it means that your application is running inside another UI5 application/container like FIORI launchpad. In this case resolving cache should be the responsibility of parent container(FIORI launchpad) holding your application

[former_member227918]

one html file must be using to run your app, that may be inside the test folder in project structure, check your app url to find html file and you can implement cache buster there.

[vishalkumar1305]

Hi Akhilesh,

yes html file is there in my project structure, but I am using component.js to run the application in HCP. So whatever I am writing in html file it will not get excuted.

[former_member227918]

find out the proper one and write in that html file, will work.

[antonette_oberholster]

Hi Vishal

This can be quite frustrating when developing apps. I always have console (f12 developer tools) open in my browser when I refresh apps. There is a setting under the "network" tab: "Always refresh from server" (IE) or "Disable cache" (Chrome). This forces the browser to load from the server instead of browser cache.

Hope this helps

Antonette

[vishalkumar1305]

Hi Antonette,

Thanks for your suggestion.
I am also using the same approach when developing the application, but I just need the permanent solution for this issue.