API 4.18 Got Console Error After Upgrade Chrome to 128.0.6613.85

Question

Hi All,

Our front-end project with ArcGIS Maps SDK for JavaScript 4.18 worked well on Chrome before it upgraded to 128.0.6613.85. After Chrome was upgraded this morning,  we got many console errors when opening a map with some graphic layers.

After some research, we found it was related to setUniform4fv() method in the Programs.js file. When the "c" is "u_sigmas", "b" comes with [underfinded, undefined, undefined, undefined ]

We can get the same error from the sample code after changing the API to 4.18.
SOandbox | Sample Code | ArcGIS Maps SDK for JavaScript 4.30 | Esri Developer

Other Browers don't have this issue. After upgrading this API  to 4.30 Chrome v128.0.6613.85 got rid of this error too, We also found the same method on API 4.30 gets a null check for "c".

Is there any idea why upgrading Chrome to 128.0.6613.85 will get this error?

AndyGup · Answer

Thanks for the update @SonnyTF. Here's a Knowledge Base article with more information on the issue: https://support.esri.com/en-us/knowledge-base/defective-chromium-128-update-and-arcgis-maps-sdk-for-j-000033499.

Related community conversation: https://community.esri.com/t5/arcgis-online-questions/map-error-in-new-chrome-update-128-0-6613-85/m-p/1526091#M61070.

SonnyTF · Answer

Hi @MichaelVolz ,

Can you share the link to that thread? I searched the community before posting this thread, but I couldn't find any topic related to this.

Thanks,
Sonny

SonnyTF · Answer

@AndyGup ,
We can confirm that upgrading to the latest version will eliminate this error. This is just out of curiosity that if any breaking change is made by Chrome in the new version that makes 4.18 not work anymore.

Thanks,
Sonny