Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Today I upgraded a Sense environment to 2023-August and then to SR3.
(With 2022-May and PostGre 14 in between)
Since upgrading to August 2023 (with and without SR) the QMC start page is bugged.
The lower half of the browser window white and not used by the page.
Hub and other pages of QMC are not affected.
Known workaround(s):
- use Edge (I think Firefox also has the bug, but did not test it today)
- ignore it, since it only affects the start page of the QMC, and other QMC pages work as usual
I have seen this on another server after updating to a version that uses PostGre 14. (But we did not investigate back then, ~3+ months ago, since we did a Rollback on that other system.)
Questions:
Has anyone else encountered this and a solution?
(Yes, I will also open a ticket with Qlik support ...)
I am seeing something similar in the HUB after right-clicking on an app. The QMC does not have the same issue as you though.
Environment is Qlik Sense August 2023 + SR3. Chrome and Edge.
Hello @shaun_lombard,
Thanks for posting.
On the Hub is a known issue that is been tracked at QB-22161.
When it comes to the QMC I could not reproduce, @john_oll , what browser are you using?
Cheers,
Albert
Issue occurred in Chrome last week.
I think (with the other customer) it was the same in Firefox.
The bug did not happen in Edge.
Hello @john_oll,
Do you perform any action to only see half of the QMC? Please share the details here with the Community.
Cheers,
Albert
I opened the QMC.
Hello @john_oll,
Is still reproducible as I did not yet managed to reproduce? or was a one time occurrence? So it jut happened by opening the QMC on the browser, Chrome, as per your comments, right?
Cheers,
Albert
Yes, it is still reproducable.
Status of the actual support ticket:
they are still investigating and also referred to QB-22161.
I just upgraded one of our QAP environments to August 2023 + SR3, and got the same half screen issue in the QMC, using EDGE. I did not have the issue in Chrome.
I cleared the browser cache in EDGE and the problem went away.
Hopefully that works for others.