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!

[JamesBurton1]

Lovely Friday surprise. Our Zone Lookup instant app that we use to query parcel information has stopped working for the most part. Occasionally I can get it to load but for the most part it just spins. 

[KellyHutchins]

Is your app public? If so can you share the url so we can try to track down the issue? I've been testing some Zone Lookup apps and haven't run into any issues yet. 

If your app is not public any details you can share about how its configured, the types of data etc would be helpful for us to track down the problem. 

[KimOllivier]

OK, here is my broken public dashboard. Cannot make table selector see the service layer.  Here's hoping you can identify it with this link

https://www.arcgis.com/apps/dashboards/e7c0e881e4e84f00b03be7e3abc52f36

[mpboyle]

99% of our ExB apps are built using Dev Edition and hosted locally on one of our web servers.  I'd REALLY like to use the AGO hosted version of ExB to offload resources/infrastructure/threats from our infrastructure, but days like today and updates like this, make me wonder if that's a good idea.

At least with Dev Edition, once it's built, it's built, and you don't have to worry about some update coming along and ruining things.

[GrantHoward1]

Another issue I found. And anyone with ExB apps might want to check into theirs too. I have several ExB apps that I have setup for users to make attribute edits on specific layers. And often times I have it set for batch editing so they can edit the attributes of several points or lines at a time.

How I want it:

But it looks as if this June AGOL update has reset all my editing widgets in all my ExB apps from "Attribute only" to "interact with a Map widget"
So essentially it broke the ability for my users to do quick attribute updates on several features at a time. 
And it also now selects every single layer in the map with the editing-selecting tool. It would even select layers not turned on! And it would even select the .tif raster files of the imagery layer in the map - and even if the imagery was turned off!

So because it now selects dozens of unwanted features that are not editable, the 'Edit' button is greyed out because it thinks I'm asking to Edit those features. 

 @ESRI @JackDangermond   - am I supposed to go into all my ExB apps and figure out a way to reconfigure it all so they work as desired? (and that's even if there is a fix!)

OR

Will ESRI be fixing all this mess they've created? Will they rollback some of these June 2026 Updates?

I don't see how so many GIS specialists should be on the hook for re-configuring maps and data that don't work because of a software update. We don't have the time. But yet if we don't make these fixes I'm just thinking of the many industries that are effected and how much productivity will be stymied all across North America because of this debacle (and somehow this is still not as bad as the June 2025 updates!!....yet). But frankly, with how often this happens, I'm thinking what's the point in trying to fix things, ESRI will break it on me again anyway.

[JonathanMcD]

Whilst I welcome quarterly updates with some additions being super useful, ESRI really don't make it easy for us. It's almost as if the devs work away in their own little silo, oblivious to just how wide and varied the tech can be used. 

Just been ranting in Instant Apps about now having to create a brand new gallery application for Instant Apps due to the update as, well, existing one can't be edited, then on creating the new one - does it publish and share ... of course not! Ok, we've got a more mobile friendly app out of it, but can I set different responsive layouts to ensure our desktop users are not faced with a Minecraft looking app ... no, can I define how many cards per row... no ... will I have to review the 40 odd plus Instant Apps in this gallery .... yes... do I hold out for any freetime this weekend to myself .... no! Do I expect to be able to re-publish the items needing updated ... equally no.

There are times it feels we are given with one hand and with the other a whole load of stuff is taken away.

To be clear, I don't want an AGOL environment is slow to keep up with modern requirements...but geez.

[AndrewSpencer]

We're having the issues where users are not able download shapefiles or geodatabases from our Open Data site - the message is that the download exceeds the 2GB limit. It certainly doesn't (or shouldn't - if it does there's another issue). E.g. Schedule of Native Title Determination Applications | National Native Title Tribunal. Download to KML is fine (18.4MB). This appears to be a recent development - I'm assuming following the June update.

[Clint_Lusk]

I don't have anything useful to add, other than wanting to add my voice to the issue. 

The dashboard and FME changes alone have stopped my customers from being able to do their normal reporting with our tools.  This might push them to use Tableau or some other solution if we can't get this reversed in time.

[valenj88]

No response from ESRI?

[GrantHoward1]

ANOTHER issue. Well I found this issue out on Friday after the June AGOL update. But I finally made some progress on it.

I have had several users crashing out on Field Maps. But weirdly only on some maps. 
Through troubleshooting I think I've determined that the latest version of Field Maps is (part of) the culprit.

If user has the newest version of Field Maps installed (version 26.2.0 on iPad or 26.2.1 on iPhone) then SOME maps will crash.

Next Step = figure out WHY those SOME maps crash and others don't crash.

But if a user has DOES NOT have the latest version of Field Maps installed they should experience NO CRASHING at all on any map.

I did create a workaround last week. For one of the maps that was crashing I created a really-scaled-down version of the map with a lot less layers and it seems to be working fine for all users. It's just not very user-friendly without the other layers that add to the user-friendly-experience.

So whatever ESRI did when they updated Field Maps (which I think was on or around June 25th) they caused SOME of my maps (we have lots!) to not work in Field Maps.
Does ESRI do absolutely ZERO testing before an update!?!?
All the crashing webmaps work perfectly fine on a PC.
I have had our corporate GIS team issue a ticket with ESRI, but I'm not holding my breath on a resolution anytime soon.

So what is in those "crashing" maps? special symbologies? layers hosted in a particular manner? too much data load? I have no clue at this time. Still troubleshooting.

Has anyone else experienced crashing issues with Field Maps?

Also, we are dealing with localized flooding in our County, and Field Maps has been heavily relied upon during this flooding event. I have had some long days lately and when GIS is supposed to be saviour in a moment like this it's instead a point of frustration for many people!

You know how ESRI (or ESRI partners) always have those feel-good-presentations at their big UC in San Diego about how "GIS Saved the Day", wouldn't it be a nice change if I were to present about this experience we are going through now and how "GIS Was No Help At All" (joking, but not really).

DO NOT UPDATE FIELD MAPS