SPFx ListViewCommandSet Extensions are no longer being loaded when switching list context in side navigation!

[frevds]

Category

• Bug

Describe the bug

Okay, let't try that again in the right section.

I registered a ListViewCommandSet Extension for a list.
But the extension is not being loaded, if I don't directly navigate to that list:

If I open the list page for a list for which the extension is activated, the extension gets loaded (constructor called, onInit called).

If I open the list page for another list for which the extension is not activated and then navigate to the list for which it is activated, using the navigation tree, the extension does NOT get loaded.

Also, if the extension was loaded for a list and the user switches to another list using the navigation, any extension activated for that list does not get initialized (constructor or onInit is not being called again).

Finally, the onListViewUpdated-Event never worked.

This issue makes list view command set extensions quite useless and breaks our product.
Is there any fix coming for this or should we move on to generic extensions loaded for every page?

Steps to reproduce

Use the yo generator to create a new ListViewCommandSet and try on your own to get it loaded for a list if you don't directly navigate to it (in SharePoint Online), see details above.

Second problem: the onListViewUpdated-Event never fires, no matter what you do in the ListView (provided the extension was loaded at all).

Expected behavior

Extensions should be loaded for lists on which they are registered, when you navigate to the list (using the navigation). Currently they are only loaded if you directly enter the correct list when opening the browser page, not when navigating in the tree (where the page does not reload but merely React controls get rerendered). This behaviour did work before, but is now broken.

Second problem: Changes in the selection of the list view should fire the event. Maybe even changes to the list context (navigating).

Environment details (development & target environment)

• OS: Windows 10
• Target Environment: SharePoint Online
• Framework: Node.js v10
• Browser(s): Chromium Edge latest
• Tooling: SPFx v1.10.0
• Additional details: Suspecting latest changes in SPO, client and solution did not change

Additional context

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[chr-sad]

Can confirm the problem in our SPFx v1.10.0 CommandSet Extension as well. The CommandSet is only loaded correctly if directly accessed. If we use left navigation, the extension is not initialized an onListViewUpdated is never fired. If we reload the page with F5 or STRG+F5 the extension on the same list is loaded and works till we navigate to another list in the left navigation.

[RowanAdvisors]

I would also like to point out that we are experiencing the exact same issue, but filtering the view even when navigating directly to the list/library causes the command set extension to bug out and stop working.

[chr-sad]

@RowanAdvisors I just tried to reproduce the filtering issue but I can not confirm a problem here. At least in our solution on our tenant even when filtering is active, the CommandSet Extension works correctly for our use case.

[frevds]

Yes same for me, filtering does not do anything bad to our extension, but then our extension does not add any toolbar buttons. What does "bug out and stop working" mean in your case @RowanAdvisors?

[Debopoma-netwoven]

I am facing the same issue:When the document library is opened for the first time from quick launch menu(left navigation menu) it loads the Command bar spfx extensions But when we switch to another library from quick launch it does not refresh the whole page and as a result
this time the command bar spfx extension does not load.It only loads after we refresh the entire page/press F5

[barisbikmaz]

Same here. Command only appears on the first list. When navigating to another list over the left navigation the command bar is not shown anymore.

[69mustang302]

I just upgraded to SPFx v1.10.0 and can confirm this behaviour. When navigating to another list using the quick launh, the commandbar does not refresh nor is there any hit on onInit of the BaseListViewCommandSet.
Currently this is blocking our corporate deployment.

[frevds]

@69mustang302 Are you implying that this is not a SharePoint issue but a SPFx framework issue, i.e. does this all still work with SPFX < 1.10?