Error viewing changes to Experience Builder apps with ArcGIS Assistant (AGOL)

[HaydenRickard]

Apologies if this has already been posted/solved already!

My organisation has recently started creating apps using experience builder in AGOL, rather than WAB.

In the past, we would have dev, test, and prod versions of WAB apps and apply changes to each by copying json across using AGO/ArcGIS Assistant (and repointing web map/feature service URLs etc). This worked well and we could see the changes when editing the prod version of the WAB app.

This does not seem to work for experience builder apps though, as changes made by copying json do not show up in the edit interface, but do when accessing the app directly.

I've added three screenshots that show this below (all after json has been copied).

• Viewing the app via URL after the json has been copied (text change and map added)
• The app in the edit interface after the json has been copied (text unchanged and image rather than map)
• Confirmation that the json has been changed

Any help with this is much appreciated! Being able to make quick changes/bug fixes for the prod version via the normal edit view is very useful and would be great if it can be fixed.

[jcarlson]

I don't use EB on AGOL, and almost exclusively use the Developer Edition, but when I look at the files that a single Experience is using, there's more than just one JSON file.

From your screenshot, it looks like the AGO Assistant is seeing the config.json file. EB has the newer feature of separating saving from "publishing", so there's a built-in separation between your latest edit and what the users see when the app is accessed.

In the Developer Edition, the editor interface accesses a separate tmp folder. I would guess that the AGOL version is doing something similar. You're only able to copy the JSON to the published version of the app, but the files in that tmp folder that the editor uses are still stuck at the older version.

Are you clicking "publish" before copying the JSON? To be clear, you probably need to click "publish" on both apps (source and destination) before copying the JSON. Publishing the app tells it that it no longer needs the tmp files, because there are no unpublished changes to track.

[HaydenRickard]

Thanks for the explanation, it helped a lot and made the way experience builder functions behind the scenes make more sense.

Both apps had all changes saved & published before copying the json across, so that doesn't seem to be the issue unfortunately.

[ShelleySchulte1]

Hello! Did you ever find a solution for this? My organization does the same thing, we have dev and prod environments.