Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Everyone-
I came across this strange issue with Sense HUB where clicking on an application does not render the application in chrome after we have updated the browser to the latest version, upon invoking the Developers console I see the following message Uncaught Syntax Error: Unexpected number; and this error is associated to my application GUID.
if i downgrade the browser to the lower version, everything works fine, if i use Firefox, it works fine as well.
I am wondering if anyone else has seen similar behavior?
Hello Zain - thanks for your findings, I will report this to R&D and see what they say.
Regards,
Mike T
Qlik
In the mean-time, can you please provide more information about the Qlik Sense software version?
Regards.
Mike T
Qlik
Michael,
thanks for the response, but i can't upload the QVF' or the log files here.
can i send them to you in an email?
Yes - I will private message you.
Michael, have you made any progress on this issue?
Many of my users were reporting blank screens so I upgraded my Chrome from 40 to 41. Immediately I had the same blank page issue. Hub loads fine, the apps load blank pages.
Any help would be appreciated.
Hi Jin, I never received the QVF from Zain - can you send me one by attaching to this thread?
Mike
unfortunately, all three apps have ton of confidential stuff on it so i
can't easily post. However, i have verified that it's due to the chrome
auto update from 40 to 41. It works fine for everyone on 40. 41 and the
Canary version of chrome all have same issues. i even upgraded my browser
on purpose to test and it's true.
On Thu, Mar 12, 2015 at 12:25 PM, Michael Tarallo <qcwebmaster@qlikview.com>
Hello,
Same issue is on the mobile devices. After i updated my Android phone's Chrome browser i cannot view any application that are on the hub.
Michael,
I have emailed you the QVF, however I would like to let you know, if we upgrade to chrome 41 or higher the application rendering does not happen, so our work around was to either enable the JAVA console and clear out the JSP error or downgrade to version 40 and disable the chrome updates in registry.
Please let me know if this helps.