WAB killed by Chrome 51

18780
44
Jump to solution
05-25-2016 02:49 PM
BarnabyRockwell
Occasional Contributor III

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

44 Replies
DavidWilton
Occasional Contributor

They are moot for now, but keep in mind that this is a temporary fix, I think chrome will release this update again because it matches the spec,. I'm sure esri will have patches ready by next time, but particularly if you have older versions of WAB running I would leave the patches in place. Older versions may not be a priority for patching.

JunshanLiu
Occasional Contributor III

I upload a patch for WAB2.0, this is the link: Web AppBuilder 2.0 patch for Chrome51

Please download and have a try.

BarnabyRockwell
Occasional Contributor III

Thank you very much, Junshan Liu.  That works perfectly.

Here is a similar patch for WAB Dev 1.2:

Web AppBuilder 1.2 patch for Chrome 51.0.2704.63

A similar patch for WAB Dev 1.3 is available here:

Web AppBuilder 1.3 patch for Chrome 51.0.2704.63

Cheers,

Barnaby

0 Kudos
ThomasColson
MVP Frequent Contributor

This is now fixed with the latest Chrome Release 51.0.2704.79. See this Chrome Bug Report for details of testing.

BarnabyRockwell
Occasional Contributor III

It appears that WAB Dev 2.0 3-d apps cannot be edited using Chrome 51.0.2704.84.

Untitled.png

0 Kudos
Jianxia
Esri Regular Contributor

Barnaby,

I was not able to reproduce the issue with Chrome 51.0.2704.84. What's the error in the console?

Thanks,

Jianxia

0 Kudos
BarnabyRockwell
Occasional Contributor III

Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.

I think that warning is for init.js:190

-----

Chrome Version 51.0.2704.84 m (64-bit)

Win Server 2012 R2 Standard x64 (via Remote Desktop)

WAB Dev 2.0

3-d app editing.  2-d app editing is fine.

-----

When I try to launch the 3-d app in Chrome from within WAB Dev 2.0, I get the same "3D web apps aren't supported" message, and then this in console:

http://myserver:3344/webappbuilder/apps/7/images/shortcut.ico Failed to load resource: the server responded with a status of 404 (Not Found)

(and indeed that icon file is missing from that directory, but if I copy that icon file in there from a 2D app, I still get the same error in Chrome)

If I use IE11, there is no issue editing 3D apps.  There is also no issue when editing 3D AGOL apps using Chrome.

Note that my WAB Dev 2.0 has NOT been patched using Junshan Liu's patch.  I removed that patch when the fixed version of Chrome was released.  Should I apply that patch? 

          -Edit:  applying the patch doesn't fix the problem.

0 Kudos
BarnabyRockwell
Occasional Contributor III

The above is still true for Chrome 51.0.2704.106 (64-bit).  Note that if a WAB Dev 2.0 3-d app is exported and deployed, it works fine in Chrome.  The issue occurs only if a 3-d app is edited or launched from within WAB Dev 2.0 using Chrome.

If esri can't duplicate the issue, perhaps it is caused by organizational group policies for Windows Server and/or Chrome.  I don't know.

0 Kudos
JunshanLiu
Occasional Contributor III

Is this still the same error? This looks strange.

0 Kudos
BarnabyRockwell
Occasional Contributor III

Yes, I'm getting the same error:

Untitled.png

Perhaps the issue is related to the fact that the Chrome browser is installed on a Windows Server 2012 VM with no graphics card - I'm running it via Remote Desktop as I wrote above.  Is it therefore a WebGL issue?  I now also get the error if I try and open an AGOL Web Scene (3-d) in the Chrome browser on the server. 

Untitled.png

Scene viewer requirements—ArcGIS Online Help | ArcGIS

Again, there is no issue viewing and editing AGOL Web Scenes and 3-d apps using either IE11 or Firefox installed on my server.

0 Kudos