Sporadic issue with Classic Web Maps not working in Chrome v.142.0.7444.60

[JackBovee]

Our Chrome web browsers happened to update overnight to version 142.0.7444.60.  Now, whenever we try to access an WAB using the Classic Web Map Viewer (or any map using the Classic Web Map Viewer), none of our hosted layers are available.  Everything is visible and functional still if you open the map in the new Map Viewer, but anything build with Classic seems to be broken atm.

We still haven't finished converting all our WAB applications over to Experience Builder yet, as I had assumed they would continue to work until next spring.

[RussRoberts]

I am not able to reproduce the issue. If you have a map that is showing this and can share you can invite russell_jsapi to the group with the maps and layers and I'll take a look.

[JackBovee]

Russ,

We only seem to be having the issues with Windows 11 and Chrome build 142.0.7444.60.

Here is one of the WAB applications that are having issues:
https://hubbardcounty.maps.arcgis.com/apps/webappviewer/index.html?id=405588666bba4397982b98b3fd382f...

Here's the underlying web map:
https://hubbardcounty.maps.arcgis.com/home/item.html?id=418bec418d7f475fb6957d53bc4fa468
Note that if you open it in the new Map Viewer, it works just fine.  Only Classic seems to be having issues.  Unfortunately, several of our older WAB applications do not play nice with the new Map Viewer, so we've been forced to use Classic. 

Below is a screenshot of the errors we're getting when using Chrome of that build.  Any of the County hosted layers are not working at all.

Also note that this is only impacted by Chrome Browsers on that particular build.  Firefox and Edge appear to not have any issues currently.  The previous Chrome build (v. x.59) also had no issues.  I've not been able to fully test off network yet to see if it is an internal only issue.

[RussRoberts]

I am not seeing this issue on the latest version of chrome using the web map and WAB app you provided.  That error above makes it look like the services are either timing out or no longer accessible while the app is loading. If you are able to look at network or console logs while loading these maps and apps and catch any errors can help us see what the issue could be. I'll keep spot checking to see if I get any loading errors still. 

[JackBovee]

Just to confirm, you are running Chrome version 142.0.7444.60?

Looking at the Chrome console when trying to load up that particular WAB, this is the first of many errors that occurred:

All the errors appear to be due to "blocked by CORS Policy".

[JackBovee]

So IT just found out that there was a change in the x.60 build of Chrome that might be the root of the problem.  There is apparently a Local Network Access check that's required to make this work.

[Jamie_Leitch_CNF]

@JackBovee  I am noticing issues with a Survey123 widget in an Experience Builder app in Portal (survey not accessible).  This started after upgrading to Chrome 142.0.7444.60.  Where did you access those settings?

[George_Thompson]

Take a look at this Chrome blog: https://developer.chrome.com/blog/local-network-access

[JackBovee]

Interesting.  I can see the point, but it's currently rather inconvenience.  Didn't realize this had been in the works for some time.

I suppose that's going to impact anyone trying to access ArcGIS Online that's utilizing GIS resources that are hosted internally.  Thankfully we're not a large county, but I envision this being an absolute nightmare for an urban area.


I'm assuming there's not really a viable solution on the hosting side to bypass this issue?  It is odd it was only impacting the resources using the Classic Webmap Viewer.

[Jamie_Leitch_CNF]

It impacted my Experience Builder app hosted in Portal with a Survey123 widget also hosted in our Portal - the Survey123 widget was showing "survey inaccessible", even when I own the survey and was logged in to Portal with admin rights. And the map in the app was built using Map Viewer (not classic). I could see this being a real pain for some.