H5 SDK shows an old version

Hi!

I keep on struggling with some type of cache when developing H5 SDK applications.

I usually upload an SDK "hundreds" of times through the H5 Administration Tool, I always get the latest version of the SDK application.

However, suddenly when uploading a new version, the SDK is showing an old version.

I've verifed the uploaded code, and it is the latest version, but for some reason the M3 "Container" shows a cached version of the SDK.

I have tested separate browsers, and even different computers, but for some reason the application still seems to be showing an older version.

Have any of you managed to "refresh" this magic cache?
Why does this happen?

Find more posts tagged with

M3 Development

Accepted answers

All comments

Legacy Contributor

We also have this problem and it is really annoying.. as I understand a fix was released for this in the september release but we still have issues.

2023.09.00

M3CE Core Technology - H5

Defect

Avoid caching of mne/apps index.html

Expires property in the response header has been decreased to 1 hour to remedy problems related to cached index.html.

Deploying new H5 SDK apps doesn't update the current application, even after refreshing the browser. One way to see the newly updated H5 SDK app is to do a "hard refresh" of the browser (common shortcuts include CTRL+SHIFT+R, CTRL+F5, SHIFT+F5, holding CTRL when pressing the refresh button), another is to open it in a new session by logging out and restarting the browser.

To remedy this the Expires time has been shortened to 1 hour.
ADDITIONAL REFERENCE:
JR-6243371

Legacy Contributor

I had this issue lately as well. So every time I need to upload and test a new version of the SDK I had to clear cookies and cached data from my browser and then upload the new version. It worked for me with this "annoying" way.

Wichtige Lösungen in der Wissensdatenbank Dezember 2011.pdf

Legacy Contributor

So you suspect it has to do with the cache of the upload, rather than the rendering?

Legacy Contributor

I've just created a support ticket with this information and a link to this community page.

I'll update this thread when I get some more information.

Legacy Contributor

Have you concluded that the cache clearing always works for you?
I still have issues with this, and I'd say it's even more problematic than it was before.

79060_LP31VsLP64_3.xlsx

Legacy Contributor

Has anyone heard anything regarding this issue yet? It's still present and very annoying.

Stewart Rutledge

One option is to open devtools, choose the network tab and check a box that says something like "Disable cache", it's a little different for all browsers, but they all have something similar.

If you have devtools opened, and that checked, it will always fetch the latest version. This isn't great for users, but it's enough if wanting to test within the customer environment.

Stewart Rutledge

One option is to open dev tools in your browser and disable cache on the network page

If you do this before opening your H5 app, it should always open to the latest version. Not a fix for end users but a workaround for users.

Stewart Rutledge

One option is to open dev tools in your browser and disable cache on the network page

If you do this before opening your H5 app, it should always open to the latest version. Not a fix for end users but a workaround for users.

Copyright © 2025 Infor. All rights reserved.