Community
Select to view content in your preferred language

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

1018
15
Jump to solution
a week ago
JackBovee
by
Occasional Contributor
a week ago

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.

0 Kudos
15 Replies
cepsgis
by
Occasional Contributor
a week ago

It is. Trust me.

0 Kudos
Jamie_Leitch_CNF
by
Frequent Contributor
a week ago

yes this solved my issue, thank you!

JackBovee
by
Occasional Contributor
a week ago

The Chrome settings were in the browser itself, just to the left of the address bar.

JackBovee_0-1762371697131.png

 

cepsgis
by
Occasional Contributor
a week ago

This is impacting all services in web maps consumed by our EAM solution. Dashboards, surveys, and Experience Builders are also affected, and field staff are now reporting issues accessing data. 

0 Kudos
MichaelB25
by
Occasional Contributor
Wednesday

I've been working on a similar problem this afternoon. Only in updated Chrome browser several of our imagery basemaps weren't displaying. Enabling "local network access" (either from pop-up, or "site information" icon to left of URL) resolves problem.

I'm guessing that AGOL apps are referencing what Chrome sees as the local network. This is a broad list, I'm guessing a local loopback may be to blamed, but unsure. See: https://wicg.github.io/local-network-access/#non-public-ip-address-blocks

0 Kudos
Charles_Blanchard
by Esri Contributor
Esri Contributor
yesterday

Hello @JackBovee,

 

This behaviour is due to an update in the way Chrome handles Local Network Access checks. You can read more about that update here: https://developer.chrome.com/blog/local-network-access.

For the time being, until the issue is fixed by Esri, you can utilize the following workaround. To avoid the inconvenience of having to constantly block or allow Local Network Access, you can go to chrome://flags/ and set Local Network Access Checks from Default to Disabled, which restores the behavior prior to the Chrome 142.x update.

Please feel free to reach out if you have any further questions!


Charles Blanchard

Associate GIS Analyst

Esri Canada

0 Kudos