January 2019 Browser Cache Issue

[smithry3]

Is anyone else experiencing the browser cache issue with the January 2019 release that impacted the August 2018 release.  I upgraded from the March 2018 release to January 2018 and my reports have a "Data loading" message with a spinning icon that spins indefinitely.  I'm using chrome.  Is there anything I can do to not have users have to clear their cache in order to use reports on Power BI Report Server?

Here is the August 2018 issue I referenced above.

https://community.powerbi.com/t5/Issues/Report-Server-August-2018-Massive-show-stopper-bug-where-use...

Thanks,

Ryan

[JonathanP]

Have the same kind of issue.

Since January 2019 (and like we had with August), some users had issues with the existing Power BI reports.

Issues are:

• Linked objects (link to bookmark) are not working anymore
• Some visuals "still loading" and never appear

Same issue on Chrome and IE.

Same solution: clean the cache/reset the explorer properties.

That's really disapointing, we can't ask our users to do such manipulation every 6 months...

[Jacky]

The issue is not resolved yet.

We still have problems with +/- icons in chrome (after clearing all history and cache files)

This is after intalling the version from 30/01/2019...

and timeline for the fix ?

thanks

[rpatkar · Accepted solution]

Hi Ryan,

The browser cache issue was fixed in Auguest 2018 relesae but still needed one final time that users would need to clear their browser cache. Users upgrading from Aug 2018 to Jan 2019 should not be seeing the browser cache issue.

In your case, since you are upgrading from March 2018 to Jan 2019, your users will need to do one final browser cache refresh after which we do not expect this to be needed again.

Was discussed @ https://community.powerbi.com/t5/Report-Server/June-2018-Release-of-Power-BI-Report-Server/td-p/4297...

Thanks,

Rohit

[BIXL]

What about this issue ?

anyone else still has this kind of problem.

I'm taking about the +/- ikons in the browser.

we work with chrome and still face this issue even after clearing cache.