topic Re: Did everyone see this issue? in ArcGIS Enterprise Questions

Did everyone see this issue?

Dan_Brumm — Wed, 12 Jun 2024 19:11:55 GMT

I feel like this is kind of a big issue that I just happened to see.

Problem: Impact of Google Chrome and Microsoft Edge 127 Updates on ArcGIS Enterprise (esri.com)

Re: Did everyone see this issue?

ZachBodenner — Wed, 12 Jun 2024 19:23:48 GMT

Yeah that kind of seems like a thing that should get emailed to every single ESRI customer, and probably announced much much earlier since the patches will be available for only the newest Enterprise versions. That's really unfortunate.

Re: Did everyone see this issue?

CodyPatterson — Wed, 12 Jun 2024 19:31:33 GMT

Very curious why this wasn't something released in a newsletter or sent out via email. I assume a very small percentage of people are moved onto 11.3 so the majority of people using Enterprise will be impacted by this. Hopefully the updates come out shortly because major users will have quite the time working with this, especially if it doesn't get announced and they're blindsided.

Re: Did everyone see this issue?

DavidColey — Wed, 12 Jun 2024 20:26:27 GMT

This is a fairly recent post on this from May 5 in the ArcEnterprise Community:

https://community.esri.com/t5/arcgis-enterprise-questions/chrome-developer-console-warnings-on-several/m-p/1418487#M39404

It's not just ESRI components, it's any web components anywhere that still reference mutation events. . . .

I'm glad to see ESRI is aware and on it, at least

Re: Did everyone see this issue?

Scott_Tansley — Wed, 12 Jun 2024 22:37:58 GMT

To be fair Esri have been warning of this potential outcome for nearly 18 months, ever since the discussion that JSAPI 3.x was to be deprecated. The warning has been open book. I would imagine that Esri are early adopters of Chrome/Edge browser versions, and may only have had a few days/weeks to see this and deal with it.

https://www.esri.com/arcgis-blog/products/js-api-arcgis/developers/arcgis-api-for-javascript-version-3-x-retirement/#:~:text=However%2C%20browser%20updates%20may%20introduce%20new%20issues%20to%20apps%20running%20on%20the%203.x%20API%2C%20resulting%20in%20performance%20issues%2C%20feature%20malfunction%2C%20or%20even%20crashing%20applications.

Re: Did everyone see this issue?

ANH — Thu, 13 Jun 2024 01:52:47 GMT

Thank you for reposting this and getting it more attention, @Dan_Brumm. Much appreciated

Re: Did everyone see this issue?

RyanUthoff — Tue, 18 Jun 2024 15:56:20 GMT

I only found out about this because that support article showed up on my "suggested" sites to visit in Chrome. This absolutely needs to be communicated with all Esri customers via email or some other notification. Anytime there is a "breaking" update, whether it be through Esri or another program that interacts with Esri, there needs to be a mass communication about it. Unless if the expectation is that the burden is supposed to fall onto the customer to constantly check Esri's support/knowledge base and/or geonet for this kind of information.

Re: Did everyone see this issue?

RyanUthoff — Tue, 18 Jun 2024 16:35:23 GMT

While I agree Esri and others have known about this potential outcome for 18 months, that also means they've had 18 months to mitigate this issue in advanced as opposed waiting until a month before Chrome releases a breaking update forcing everyone to install a patch in a month timeframe before Portal breaks. I don't believe they've only had days/weeks to deal with this considering it's already "fixed" in 11.3.

Even Esri indirectly admitted in their own support article that Portal is dependent on "old, obsolete piece of web technology." My question is why is this being mitigated at the last minute when this warning has supposedly been an open book?

Edit: Not directing my frustration at you. I'm just frustrated at the situation and the lack of communication from Esri about a major breaking change.

Re: Did everyone see this issue?

Scott_Tansley — Tue, 18 Jun 2024 19:49:48 GMT

I get the frustration. But the warning 18 months ago was a generic - 'something could happen'. The specifics of that were unknown until very recently. Esri can only fix the specifics that they know about. Further, Esri are not aware of the direction that Google will take Chrome, and there could be more breaking changes to come if people stay on the JSAPI 3.x path.

The article and the current issue relate to the fact that a lot of the JavaScript in 11.1 (possibly 11.2) and earlier was predominantly JSAPI 3.x. I understand that 11.3 the bulk of the JSAPI is 4.x, which is not affected by these changes. There will be some 3.x stuff in there, without a doubt, but 11.3 is a transitionary version where WAB apps should morph to become EXB apps during this release. So the tools are available to mitigate the published issue.

Re: Did everyone see this issue?

Thomas_Puthusserry — Wed, 19 Jun 2024 11:22:12 GMT

This was communicated to us by local ESRI just a week ago. We were in 10.9 until last week, but luckily upgraded to 11.1 without even aware of the fact that patches are not available for 10.9.

Any idea when the patches would be released and any potential impacts of this when applied? There are quite a bit of concern about business disruptions and a very short window available to fix this.

Re: Did everyone see this issue?

Thomas_Puthusserry — Wed, 26 Jun 2024 08:27:52 GMT

It seems ESRI released the patch: Portal for ArcGIS Application Display Patch (esri.com)

I wonder whether there is any option to test how this looks like in the updated browser versions?

Or is this like: apply patches and wait and see when the browser updates comes through?

@Scott_Tansley any suggestions?

Re: Did everyone see this issue?

Scott_Tansley — Wed, 26 Jun 2024 08:42:56 GMT

My feeling is that you're unlikely to see any changes, other than if you review the 'network' traffic, pre/post application. The place where you will see the difference is that if you apply it ASAP, you almost certainly won't see the errors and loss of reliability that will come when the breaking change is implemented. Recommendation: Just do it.

Re: Did everyone see this issue?

spanton — Wed, 26 Jun 2024 11:07:19 GMT

Thanks for sharing @Thomas_Puthusserry . I've been stalking the initial Technical Support article since hearing about it. I was surprised to see although the article states "This article will be updated as patches become available" it looks like the patch has been available since May 30 and yet the article has not been updated.

Has anyone given the patch a go?

Re: Did everyone see this issue?

Thomas_Puthusserry — Wed, 26 Jun 2024 11:40:36 GMT

Thanks @Scott_Tansley I have installed the patch in the primary portal for test system and can seems fine. There is a Chrome beta version available : https://www.google.com/chrome/beta/next-steps.html?installdataindex=empty&statcb=1&defaultbrowser=0 if anyone wants to test how the portal will look before and after upgrade. I found this very useful

Re: Did everyone see this issue?

Thomas_Puthusserry — Wed, 26 Jun 2024 12:12:55 GMT

@spanton I just installed in our test env for the primary portal and seems fine. you can check how the portal looks before and after applying this patch via Chrome beta which is version 127: https://www.google.com/chrome/beta/next-steps.html?installdataindex=empty&statcb=1&defaultbrowser=0

I have tested this in the latest Microsoft Edge version available here: https://www.microsoft.com/en-us/edge/download/insider?form=MA13FJ, and surprisingly there is no issue to view Portal items and navigation bar in this version: Microsoft Edge Version 127.0.2651.15 (Official build) beta (64-bit).

Only Chrome beta shows the issue highlighted by ESRI.

Re: Did everyone see this issue?

spanton — Wed, 26 Jun 2024 14:03:25 GMT

Beautiful, thanks so much for sharing your knowledge! 😊

Re: Did everyone see this issue?

SBerg_VHB — Wed, 26 Jun 2024 20:22:51 GMT

Hello all, does anyone know the effect of the chromium updates on existing Web App Builder apps and other custom widgets using dojo + JSAPI 3.x?

Re: Did everyone see this issue?

WengNg4 — Mon, 01 Jul 2024 02:56:40 GMT

If you open Developer Tools with the browser(Chrome or IE), the browser does warn users if the page contains the about to be deprecated mutation event above. It might be another method you can use to check if the page/app will break.

I have yet to see this issue on Web App Builder OOTB apps unless proven wrong.

Re: Did everyone see this issue?

Pei-SanTsai — Wed, 14 Aug 2024 21:54:53 GMT

I applied the patch & didn't have any issue with Edge. Edge is the default web browser at work and that's the main one that I used. I do have Chrome on my workstation and noticed it's not displaying the global navigation bar. Wondering if anyone has the same issue?

Re: Did everyone see this issue?

Thomas_Puthusserry — Thu, 15 Aug 2024 07:21:23 GMT

Have you cleared the cache?