Document Library view displays blank page

Thanks for this comment, Paul--good to know it isn't just me! If it happens again, it's good to know that perhaps clearing the cached data will help.

Sherri

We have the exact same issue. The cause was the uBlock Origin extension in Chrome. Once we whitelisted our SPO sub-domain within uBlock Origin, the issue when away. Clearing the cache was not necessary to fix.  

Can you verify that you are using uBlock Origin in Chrome? 

I'm not using this extension. 

Thanks for checking. I was incorrect uBlock Origin was not the issue. We are continuing to get reports of the problem even with uBlock whitelisted for the SPO URL .

Not sure if this helps. When users have the issue, I see this error appear using the Chrome dev console (F12) right when the page goes blank. 

react-mini-c64a18c1.js:118 TypeError: Cannot read property 'getEffectiveViewXml' of undefined

    at u.t._updateGetItemContext (splistlightspeeddeferred-mini-e3704853.js:1360)

    at u.t.getSections (splistlightspeeddeferred-mini-e3704853.js:1360)

    at h._getSmartFilters (splistlightspeeddeferred-mini-e3704853.js:1728)

    at h.componentDidMount (splistlightspeeddeferred-mini-e3704853.js:1728)

    at h.e.<computed> [as componentDidMount] (splistlightspeedroot-mini-c4d39a8c.js:39)

    at qi (react-mini-c64a18c1.js:131)

    at ui (react-mini-c64a18c1.js:134)

    at react-mini-c64a18c1.js:159

    at unstable_runWithPriority (react-mini-c64a18c1.js:1)

    at Vc (react-mini-c64a18c1.js:159)

Not sure if this helps. When users have the issue, I see this error appear using the Chrome dev console (F12) right when the page goes blank. 

react-mini-c64a18c1.js:118 TypeError: Cannot read property 'getEffectiveViewXml' of undefined

    at u.t._updateGetItemContext (splistlightspeeddeferred-mini-e3704853.js:1360)

    at u.t.getSections (splistlightspeeddeferred-mini-e3704853.js:1360)

    at h._getSmartFilters (splistlightspeeddeferred-mini-e3704853.js:1728)

    at h.componentDidMount (splistlightspeeddeferred-mini-e3704853.js:1728)

    at h.e.<computed> [as componentDidMount] (splistlightspeedroot-mini-c4d39a8c.js:39)

    at qi (react-mini-c64a18c1.js:131)

    at ui (react-mini-c64a18c1.js:134)

    at react-mini-c64a18c1.js:159

    at unstable_runWithPriority (react-mini-c64a18c1.js:1)

    at Vc (react-mini-c64a18c1.js:159)

This is exactly the error we are seeing, both for Chrome and Edge users.

Hi Sherri,

Sorry for the inconvenience caused by this issue. After seeing your post I did a search in Service Dashboard, unfortunately I didn't find any related service incidents. Also, we could not repro the issue you met, so we would like to collect more info then help you narrow down the issue cause.

1. Please ask the user to enter the document library via other browsers(Edge or FireFox), to see whether the same problem would happen. If not, he could try going to Chrome Settings->Privacy and security->Clear browsing data->Advanced, then ticked all data and clear them. Restart the browser then enter the document library to see the result.
2. If in other browsers the problem remains, please tell me whether he could access other sites' document library. What's more, did he enter the site successfully before? It would be good if you could share us a screenshot of the problem and the version of the Windows system.

Thanks for your understanding and patience, and please feel free to post back.

Have a nice day: )

Best regards,

Oliver

Hi Oliver,

You may want to check this thread again--users from other organizations are reporting the same or similar problem, and this might provide insight. The problem doesn't seem to be a "one-off."