I created a public-facing experience builder application that pulls dynamic images into a list widget from the feature service. When a new photo becomes available, the file is replaced with the new image but keeps the same file name. That way we do not have to update the URL in the feature service. However, this poses some issues with how the image will load in the experience builder app. The new image will not display in the app until the end user clears their browser cache. This would not be an issue if this was not a publicly available app. Is there something that can be done so the image will update in the app but eliminate the need to clear the cache data and change the file name?
