Issue with Widget Caching in Experience Builder After Publishing New Version

[SumitMishra_016]

We developed a custom widget in Experience Builder (version 1.12.0) and made several changes to it. After updating the version in the manifest.json, we published the updated widget to the server. However, after publishing, we noticed that the old version of the widget is still rendering. Only when we perform a hard refresh (Ctrl+F5), the updated version is loaded. But if we press F5 again, the old version reappears.

Please let us know the solution for this, as we cannot expect users to press Ctrl+F5 every time they use the application.

Issue observed in both 11.2 and 11.0 versions of ArcGIS Enterprise.

[TimWestern]

I think this may happen in 11.3 of AGE also

When you publish a widget, are you publishing it to Portal?  
Or are you publishing it to a host website running a webserver so you can point the URL at it?

We did the later, and discovered that every time we deployed I needed to rename or delete the original folder and then because it was IIS sometimes recycling the application pool might be required. (

I think the manifest.json has to have a change in it too if I recall correctly

The manifest.json would have a "version" key and an "exbVersion" key.  I think the version key is the one that has to be changed each time you publish. (But it sounds like you tried that already)