Web app not working on chrome

[JeffreyWitkamp]

We have a portal set up for our company with a custom themed web app. Last week one of the employees complained that he could not access any feature popups on the webapp.

This week the same happened to me. I cannot use the coordinate widget, no popups are loading, and I cannot use measurement tools. Seems like all onclick content broke for Google Chrome.

Clearing cache, changing users or restarting the server doesn't do anything. There are no strange error logs.

All of this content is also working just fine on Firefox and Microsoft Edge. Really seems to be a sudden Chrome thing but I dont know how to fix it.

Also found this post from about 2 weeks ago detailing the same issue: https://community.esri.com/t5/arcgis-web-appbuilder-questions/custom-web-app-not-working-in-chrome/t...

[Banff_GIS_Department]

My case was closed and linked to  BUG-000138681 - but no real information there either. 

https://my.esri.com/#/support/bugs/BUG-000138681 

[Banff_GIS_Department]

I had to make both changes as well - had to change both the API version number and make sure we did not use apiUrl = portalUrl + 'jsapi/jsapi', in the file 'env.js' found at C:\Program Files\ArcGIS\Portal\apps\webappviewer . Many thanks!

[Dan]

I've never worked with WAB, but couldn't you download the Javascript 3.35 API to your local server and point the apiURL to it?  Please keep in mind that if you do this, you'll need to manually edit the baseURL in both the init.js and dojo.js files.  Walk-through provided below:

https://support.esri.com/en/technical-article/000011974

[Brian_Wilson]

Yes, you absolutely could do that. That's the way you would have to do it to get the API to work to avoid having the browser pull the code from Esri's site. I don't know what's running js.arcgis.com but assume it's some massive high availability thing at Amazon Web Services. So in fact, for OUTSIDE customers, it's probably faster. For people ONSITE the page probably now loads a tiny bit slower. It's creating traffic on our Internet connection that was not there yesterday. What to do? 

Given that when you pull up an app, it loads the API only on the first call, and sadly given that employees here are not ALL using amazing and wonderful web maps, it's a really probably wash.

[Brian_Wilson]

If you chose to host the API locally, to save you some time, version 3 is here, scroll down to find 3.35 https://developers.arcgis.com/downloads/#javascript

NOTE -- The Esri install.html included with this ZIP says to use the version at js.arcgis.com so patching the code to use js.arcgis.com instead of a local copy is actually their recommendation.

[DonNeumann]

This fix worked for our organization. Thank you Robert.

[Banff_GIS_Department]

Thank you - this worked for us too with the addition that we did not find 'apiUrl = 'https://js.arcgis.com/3.xx' but we did have a line that took the Portal URL and appended 'jsapi/jsapi' - this had to be changed too. We  are using OOTB WAB on an Enterprise 10.7.1 set up.  

[KelleyAllenR]

My reply from an open ESRI ticket:

After further investigation on this issue, the following BUG has been written for this issue:

• BUG-000138681- User cannot identify/click on the MapViewer with Chrome version 89.0.4389.90 or higher for Portal 10.7.x/10.8.x on some machines

The solution is to use JS 3.35 but not possible with Portal since you are tied to a specific version. like portal 10.7.1 is using JS 3.28. There is multiple factors affecting this issue:

• Chrome zoom setting other that 100%
• Screen resolution (laptop size versus external monitor and screen resolution)
• Windows zoom scaling (100%/125%, etc)

YALL! I fixed my Chrome zoom setting and everything is back to normal! *mind blown*

[Brian_Wilson]

Changing settings in Chrome had no impact for me. I had to open the Display settings in Windows and change the "Scale and Layout" from "125% (Recommended)" to "100%" to get it to work. I can't leave it at that setting because my eyes are more than 22 years old. But at least now I can reproduce the problem reliably.

[Dan]

Please also see: https://community.esri.com/t5/arcgis-api-for-javascript/javascript-api-3x-map-click-event-intermitte....  The issue seems to be that older ESRI Javascript APIs are not handling the more recent chrome browser's scale <> 100%.  RobertScheitlin__GISP's solution is also how we fixed it in our JSAPI 3x app: upgrade to 3.35.  However, for some, this cannot easily be done, as updating the API breaks their custom apps.  If you search the ESRI forums you'll see that this issue of the map not firing the click event is becoming more frequent across all ArcGIS Javascript apps.  We are still looking for the actual cause and a fix that (a) doesn't include updating the API and (b) that doesn't require some action by the user to fix the problem.