Issues refreshing widgets - keep getting cached versions

Hi, I am developing some widgets. They are served up from a development server.

using chrome as the client.

Having issues getting the latest widgets off the development server, sometimes they are a few versions behind (cached).

I have tried “refreshing”, disconnect/reconnect , private browser and I get sporadically different levels of cached widgets . I have also tried deleting “application” data.

Any help on how I avoid these issues , pls?

1 Like

Sorry what does “This post was flagged by the community and is temporarily hidden.” mean? Why would it be flagged?

It means a post (reply) was flagged and resulted in the post being hidden, which means moderators and above can see the reply but for most it is hidden. The post has not been deleted.

If a moderator decides the flag is valid, then one of several actions can occur.

In your case it means you see that a reply exist but not the details.


Since I can read the reply, all I can say is that flagging was a wise decision.

Have you tried implementing Cache Busting for your widget resource URLs on the server?
I ran into the same issue while testing widget changes, so I implemented hash/version calculation based on the widget code. The resources are served like this:

ui://widgets/summary.html?v=c221706e114f3023

On my server, even a small layout change regenerates the hash on re-init, so after a “refreshing” new hashes are generated and the UI will always fetch the fresh content instead of a cache.

1 Like