Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Development that use cross-site resources may encounter issues when Chrome version 80 is released in the month of February 2020. An example of when issue may occur is when using "domReady". (https://www.cdnpkg.com/require-domReady)
The following may be registered in the Google Chrome Development Tools:
"A cookie associated with a cross-site resource at ....[URL]... was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032."
Even though this comes from the Chrome console, other browsers as Mozilla and Edge may also displaying similar warnings.
The above may currently happen on the latest Qlik Sense Enterprise and QlikView releases.
This is cause by a new CORS security standard/feature that browsers are now enforcing, or beginning to enforce as developers begin to opt in. More information is available here https://www.chromestatus.com/feature/5088147346030592 and here https://www.chromestatus.com/feature/5633521622188032 as the above error mentions.
R&D is currently working on a solution, and updates regarding this will be posted here once this information becomes available.
Known Workaround(s):
Reference: https://support.qlik.com/articles/000092955
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.