nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Trouver plus de publications taguées avec

Accepted answers

SumitMishra_016

I have changed the version key already

I raised this issue with ESRI technical team, they have raised a bug.

All comments

DanCopKac

So how do we resolve this in 11.3 and before? Currently facing this issue. After 24 hrs the widget still wont update unless the business user does a hard reload every time. Can't be expecting this of the business users.

JunshanLiu

@SumitMishra_016 This is a known issue and has been fixed in the Enterprise 11.4.

SumitMishra_016

I have changed the version key already

I raised this issue with ESRI technical team, they have raised a bug.

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)

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.