topic Re: WAB killed by Chrome 51 in ArcGIS Web AppBuilder Questions

WAB killed by Chrome 51

BarnabyRockwell — Wed, 25 May 2016 21:49:19 GMT

I just upgraded Chrome to version 51 (51.0.2704.63 x64), and now none of my WAB apps, even AGOL-based apps, will fully load. They partially load and the progress thingy just keeps spinning. On my server, WD 1.2 and 1.3 will load into Chrome and show apps, but none of the apps will load fully when launched. WAB Dev 2.0 will only partially load into Chrome, and no apps are shown. I can see that I am logged in to my organization's Portal, so that is not the issue.

Does anyone else see this? Is there some way I can configure Chrome 51 settings to allow WD 2.0 and apps to load fully?

All is normal with Firefox 46.0.1 and IE11.

My organization's default enterprise browser is Chrome, so if anyone upgrades to current version, they won't be able to use any of my apps.

Chrome 51 includes many security fixes:

Chrome Releases

Re: WAB killed by Chrome 51

TrentReeder — Wed, 25 May 2016 22:33:00 GMT

Me too!

I thought I hosed the program during widget development...

Re: WAB killed by Chrome 51

BarnabyRockwell — Wed, 25 May 2016 22:34:36 GMT

Uh-oh! Not good.

Re: WAB killed by Chrome 51

PeteCrosier — Thu, 26 May 2016 09:48:31 GMT

I'm getting issues across AGOL on Chrome 51 - Developer Tools (F12) shows the error on each affected page as "<page>:1 Uncaught ReferenceError: normal is not defined". I can't access our organisation's administration and content pages to do anything at the moment.

Re: WAB killed by Chrome 51

RobertScheitlin__GISP — Thu, 26 May 2016 12:59:28 GMT

All,

I am still using 50 so I don't have these issues. Here is a how to link about downgrading chrome:

How to downgrade to Older version of Chrome | Techdows

This would not be the first time Chrome has broke esri software with their newer browser version.

Re: WAB killed by Chrome 51

roemhildtg — Thu, 26 May 2016 13:07:56 GMT

The problem is with the version of xstyle that the javascript api uses. The issue is resolved in newer versions of xstyle. Credit goes to @tmcgee who noticed this issue awhile back on the canary version of chrome, there are a lot of details about the issue here.

css files do not load using `xstyle/css!` in Chrome Beta, Dev, and Canary Channels · Issue #552 · cmv/cmv-app · GitHub

Re: WAB killed by Chrome 51

MicahWilliamson — Thu, 26 May 2016 13:40:35 GMT

I'm experiencing issues in Web App Builder only, but not the application it creates. (foldable theme) Other than the obvious "Use another browser for WAB" Any idea of a workaround? or are we waiting on Esri for this?

Re: WAB killed by Chrome 51

PeteCrosier — Thu, 26 May 2016 14:02:54 GMT

Passed this on to UK Support - actual maps and web apps seem to be working OK for us thankfully, just can't do anything of use through our organisation's AGOL site.

Re: WAB killed by Chrome 51

George_Thompson — Thu, 26 May 2016 14:11:35 GMT

ArcGIS for Server Admin Tools for ArcGIS Online & Portal

Re: WAB killed by Chrome 51

RobertScheitlin__GISP — Thu, 26 May 2016 14:22:03 GMT

Downgrade until esri addresses this issue.

Re: WAB killed by Chrome 51

DavidColey — Thu, 26 May 2016 15:03:19 GMT

Whoa - thanks for this notice all!

Re: WAB killed by Chrome 51

DerekLaw — Thu, 26 May 2016 16:13:31 GMT

All,

FYI, the recent Chrome 51 update has caused some issues working with the ArcGIS API for JavaScript v3.8 - 3.16, which in turn affects Web AppBuilder for ArcGIS. We are currently investigating the issue and are working on a resolution. I will post a status update when we have info to share.

Meanwhile, as Robert Scheitlin, GISP suggested, please do not upgrade to Chrome 51.

Hope this helps,

Re: WAB killed by Chrome 51

ThomasColson — Thu, 26 May 2016 16:32:54 GMT

Many of us do not have a choice in when browsers are updated....

Re: WAB killed by Chrome 51

RobertScheitlin__GISP — Thu, 26 May 2016 16:48:17 GMT

Thomas,

Then just follow the link I provided to downgrade.

Re: WAB killed by Chrome 51

BarnabyRockwell — Thu, 26 May 2016 16:53:53 GMT

Exactly, Thomas! Most users here will be auto-upgraded for "security" purposes.

Re: WAB killed by Chrome 51

BjornSvensson — Thu, 26 May 2016 16:54:04 GMT

Barnaby Rockwell Robert Scheitlin, GISP et al,
Yes, there is a problem with the Google Chrome 51 (and Chrome Beta 52). The Chrome code change was however reversed and is not an issue in Google Chome Canary 53. Hopefully, this reversed code will also make it into Chrome 51 as well. See Issue 597500 - chromium - Pseudo and non pseudo elements don't return correct computed content value - Monorail for more details.

Meanwhile, we are working on patching the software as well. Yesterday we patched the hosted CDN version of 3.8-3.16, so applications, like WAB, using them should no longer have any problems. In addition, we are planning further updates to AGO, hopefully tonight.

Re: WAB killed by Chrome 51

BarnabyRockwell — Thu, 26 May 2016 18:27:04 GMT

Oddly, my WAB behavior with Chrome Stable 51 has changed slightly.

Locally-hosted WAB Dev apps will not fully load. - Updated 5/27/16
AGOL-hosted WAB apps will not fully load, unchanged from yesterday. - Updated 5/31/16
WAB Dev 2.0 will not load, showing no apps, unchanged from yesterday. - Fixed with patch by Junshan Liu 6/1/16
I cannot reach my organization's Portal at all. For example, I cannot reach http://myexampleorg.maps.arcgis.com/home/content.html - Updated 5/27/16
AGOL-hosted WAB apps cannot be edited using my organization's Portal. The editor hangs with perpetually-spinning progress indicator. Uncaught ReferenceError: normal is not defined - Added 5/27/16 - Updated 5/31/16

Re: WAB killed by Chrome 51

ThomasColson — Thu, 26 May 2016 19:25:36 GMT

If only it were that easy. We can't even edit the Trusted Sites in IE, (nor turn off the Enterprise Mode). Chrome is equally locked down. Air raid sirens would go off in the concrete bunker if I tried rolling back a chrome version.

Re: WAB killed by Chrome 51

George_Thompson — Fri, 27 May 2016 11:57:24 GMT

Official Blog post related to this issue:

https://blogs.esri.com/esri/supportcenter/2016/05/26/problems-with-arcgis-online-portal-for-arcgis-apis-in-latest-google…

Added a Technical Article also: http://support.esri.com/technical-article/000013156

Re: WAB killed by Chrome 51

BarnabyRockwell — Fri, 27 May 2016 16:21:41 GMT

Note that Chrome Dev Channel has moved from 52.0.2743.10 to 52.0.2743.0, indicating a reversion of some sort.

bd9df7c452f9a6aadc49214a4a09451fc726be92 - chromium/src - Git at Google