Chrome Update 58.0.3029.110 seemingly breaks groov charts


#1

I updated to the latest version of Chrome today and none of my charts in groov are working? They just perpetually say Loading...

I tested in the latest versions of Safari and Firefox and it works fine in both of those browsers.

Below is the console log from Chrome of the errors:

/api/v0/data-logging/fetch-interactive Failed to load resource: the server responded with a status of 403 (Forbidden)
app-0.js:80 2017-05-16 12:19:07,224 [ERROR] InteractiveDataFetchOperation - Received a non-200 response: 403

_.Tc @ app-0.js:80
app-0.js:80 2017-05-16 12:19:07,225 [ERROR] InteractiveBehaviorHandler(1)::onDataLogError - Something went sideways: GENERIC

_.Tc @ app-0.js:80
app-6.js:1588 Uncaught TypeError: Cannot read property 'appendChild' of null
    at L8b (app-6.js:1588)
    at xNb (app-6.js:1585)
    at mNb (app-6.js:677)
    at lNb (app-6.js:674)
    at zNb._.Hi (app-6.js:693)
    at X3 (app-6.js:1713)
    at YNb._.nf (app-6.js:1716)
    at Lwa._.lf (app-0.js:292)
    at XMLHttpRequest.eval (app-0.js:492)
    at XMLHttpRequest.eval (app-0.js:1348)
app-6.js:1588 Uncaught TypeError: Cannot read property 'appendChild' of null
    at L8b (app-6.js:1588)
    at xNb (app-6.js:1585)
    at mNb (app-6.js:677)
    at lNb (app-6.js:674)
    at gGb._.gl (app-6.js:684)
    at icc._.Wc (app-6.js:1772)
    at icc._.Vc (app-0.js:87)
    at eval (app-0.js:87)
    at eval (app-0.js:1348)
/api/v0/data-logging/fetch-interactive Failed to load resource: the server responded with a status of 403 (Forbidden)
app-0.js:80 2017-05-16 12:19:47,478 [ERROR] InteractiveDataFetchOperation - Received a non-200 response: 403

_.Tc @ app-0.js:80
app-0.js:80 2017-05-16 12:19:47,479 [ERROR] InteractiveBehaviorHandler(2)::onDataLogError - Something went sideways: GENERIC

_.Tc @ app-0.js:80
app-6.js:1588 Uncaught TypeError: Cannot read property 'appendChild' of null
    at L8b (app-6.js:1588)
    at xNb (app-6.js:1585)
    at mNb (app-6.js:677)
    at lNb (app-6.js:674)
    at zNb._.Hi (app-6.js:693)
    at X3 (app-6.js:1713)
    at YNb._.nf (app-6.js:1716)
    at Lwa._.lf (app-0.js:292)
    at XMLHttpRequest.eval (app-0.js:492)
    at XMLHttpRequest.eval (app-0.js:1348)
/api/v0/data-logging/fetch-interactive Failed to load resource: the server responded with a status of 403 (Forbidden)
app-0.js:80 2017-05-16 12:19:47,487 [ERROR] InteractiveDataFetchOperation - Received a non-200 response: 403

_.Tc @ app-0.js:80
app-0.js:80 2017-05-16 12:19:47,487 [ERROR] InteractiveBehaviorHandler(3)::onDataLogError - Something went sideways: GENERIC

_.Tc @ app-0.js:80
app-6.js:1588 Uncaught TypeError: Cannot read property 'appendChild' of null
    at L8b (app-6.js:1588)
    at xNb (app-6.js:1585)
    at mNb (app-6.js:677)
    at lNb (app-6.js:674)
    at zNb._.Hi (app-6.js:693)
    at X3 (app-6.js:1713)
    at YNb._.nf (app-6.js:1716)
    at Lwa._.lf (app-0.js:292)
    at XMLHttpRequest.eval (app-0.js:492)
    at XMLHttpRequest.eval (app-0.js:1348)
app-6.js:1588 Uncaught TypeError: Cannot read property 'appendChild' of null
    at L8b (app-6.js:1588:216)
    at xNb (app-6.js:1585:342)
    at mNb (app-6.js:677:290)
    at lNb (app-6.js:674:473)
    at gGb._.gl (app-6.js:684:370)
    at icc._.Wc (app-6.js:1772:124)
    at icc._.Vc (app-0.js:87:378)
    at eval (app-0.js:87:302)
    at eval (app-0.js:1348:239)


#2

I updated my Chrome this morning to the same version. (Version 58.0.3029.110 (64-bit))

Working fine here.

Are you using the 32 bit version or the 64?

[Edit - Also, is the trend that breaks for you a classic or interactive?]


#3

Are you using the 32 bit version or the 64?

64 bit

is the trend that breaks for you a classic or interactive?

Interactive


#4

False alarm I guess… I closed Chrome all the way down and started it fresh again and it’s working now???


#5

Ah. I was just re-reading the error you posed and the 403 just now jumped out at me… It means that your user/pass got messed up in the Chrome update.
I was going to suggest that you restart chrome, or log out and log in to groov again, either of those should have fixed the browser credential cache.

Thanks for getting back to us that its working.