June 2026 AGOL Update - issues....so many issues

[GrantHoward1]

Where do I start?
Field Maps access issues - but somehow only affecting some users. And somehow only affecting some maps. And not data layer related, because I can duplicate the map and then affected users can use the new map. Not cache related, because issues persist with using a device that NEVER had Field Maps previously installed.

Then, I just find out that my editing tools in some Experience Builder apps is not working. The editing tool is selected EVERY layer in the map, even when they are turned off. And those layers are not even editable/selectable in the first place!

So tired of ESRI treating their customers as the sandbox environment for their updates.
And yet, ESRI Health Dashboard is all green showing no issues. But here on this community board it's full of users with random issues after June 2026 update.

Please fix it all! Or we'll have to be telling our field staff of over 100+ to get paper and highlighters ready!

[__JackCharde__]

Also experiencing strange issues only after this June '26 update. I've a client whose hosted feature layer is not displaying properly in their web maps with filters applied, even though there is data that matches filter conditions. You can get it to display for a second by clicking on the layers and bringing up the layer configuration pane, but then it disappears again. 

I'm also seeing strange behavior of ArcGIS Notebooks. WAY more frequent disconnection and the kernel dying. It is very frustrating.

[RussRoberts]

If you can share that web map where you are seeing the filtering issue I can take a look. If you cant share it publicly you can invite russell_jsapi into a group and I'll take a look.

[SoniaDickersonTCC]

Just adding to the list - but with a work-around as well.

We noticed that after the June 2026 AGO Update, some the Layer filters in the Maps would get incorrectly formatted when editing the filter via the Map interface, which is what we've always done.  

A query that had more than 3 conditions, like the following:

(field1 = 1) AND (FieldCount1 <> 0 OR FieldCount2 <> 0 OR FieldCount3 <> 0 OR FieldCount4 <> 0 OR FieldCount5 <> 0)

Would get formatted to:

(field1 = 1) AND (FieldCount1 <> 0 OR FieldCount2 <> 0 OR FieldCount3 <> 0 ) AND FieldCount4 <> 0 AND FieldCount5 <> 0

As a work-around we stopped using the filter via the Map Interface and use Arcgis Assistant to edit the definition expression in the JSON Editor.

[RussRoberts]

If you can share a map showing this issue I can take a look. You can invite russell_jsapi into a group and I'll take a look if its not shared publicly.

[RussRoberts]

I've created a repro case and looking into this. 

[esthompson]

Late to the game on this, but it seems like dashboards have been taking some hard hits. We are experiencing a niche issue with custom basemaps not displaying at all in our dashboards. They are visible in the web maps when saved, but will not appear in the map widget in the dashboard. If we turn on the basemap switcher widget and select the custom basemaps within the dashboards, then they will display.

Conveniently, ESRI created basemaps appear just fine. Tried in incognito, clearing my cache, checking the projections, ...all the usual troubleshooting issues. This is SPECIFIC to just the interactions with dashboards.

[ghedger_utilisource]

Thank goodness for this thread. I hope ESRI takes this seriously, I'm putting in a ticket now due to the fact that our related records in web map viewer are now read-only and we can't figure out how to fix it. The telling part is that in Field Maps they are fine, still editable, no issues. This update has caused us to put in so many extra hours fixing things that were working just fine prior. 

[spatialdude2025]

Nearly two months after the update, and I'm still chasing my tail fixing issues. I'm a one-person team managing thousands of feature layers, over 200 backend automations, dashboards, Experience Builder apps, Survey123 forms, maps, and more.

We had at least one issue with nearly 70% of our dashboards, especially where we were using custom Arcade formatting. Indicators broke, and there have also been ongoing performance issues with maps. It feels like something changed in the rendering engine this year because large maps are now painfully slow to load and render, even with all visibility settings configured, spatial indexes, seems like they messed up the automatic cache too.

It definitely feels different from before, and performance seems to have taken a hit.

[JamesRobe]

@TianWen  @RussRoberts 

Thanks for the fix on the Experience Builder Edit widget, specifically the part about
features from unconfigured layers no longer being selected.

Flagging that the same behavior is still present in the Map Viewer Edit pane. Drag/marquee
select in the Edit pane returns features from layers that aren't editable, so a user trying to
select a handful of points also picks up everything underneath from the reference layers. Started
with the June 2026 update. Persists after a hard refresh and in an incognito window.

The clearest example in my map is a reference layer whose service capabilities are `Query,Extract`.
It has never advertised `Editing` at any point and is not editable by any mechanism, the marquee
still selects it.

I also set the operational-layer `capabilities` property to `"Query"` in the web map JSON on every
layer I don't want edited, per the web map spec ("Lack of `Editing` in this string indicates
editing is not allowed"). That correctly disabled editing on those layers, but had no effect at all
on what the marquee selects. So the Edit pane's hit-test doesn't appear to consult editability from
either the service capabilities or the web map override.

Is Map Viewer covered by the same fix that went into the ExB Edit widget, or is it tracked
separately? Happy to share the map if that may help.