SPFX ListView Command Set Extension not loading

[veerasekarmeiyappan]

Category

• Question
• Typo
• Bug
• Additional article idea

Expected or Desired Behavior

On "Gulp serve" SPFX ListView Command Set should redirect to SP Site list view page and should render a new button named "Command Two" on the list view command tool bar

Observed Behavior

On "Gulp serve" SPFX ListView Command Set redirected to SP Site list view page as expected but didn't render the new button "Command Two" on the list view command tool bar. No errors or warnings found in page and VS code Terminal window

Steps to Reproduce

1. Created a new SPFX ListView Command Set as in Microsoft site
   https://docs.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api
2. Opened in VS code
3. Updated the PageURL in "serve.json". No extra code added.
4. Ran "Gulp serve" in cmd
5. Browser will open the SP Online site list view "allitems.aspx". Click "Load Debug Scripts" in the "Allow debug scripts" pop up window
6. The list view will load as in OOTB view but the expected button "Command Two" was not available

Submission Guidelines

Sure this is not a big bug as it has worked earlier for many users, may be a regression bug.
But blocked in creating such extension at all.
SPFX extension also didn't work here is the open issue #4374

Thanks for your contribution! Sharing is caring.

[msft-github-bot]

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

[veerasekarmeiyappan]

Here is the spfx listviewcommandset project code I used. I have removed the nodemodules folder due to space.
https://github.com/veerasekarmeiyappan/SPFXIssues/invitations

[JonathanJourdan]

Same problem here #4338 and here #4219
But a workaround by @jackpoz work for me ! :)
#4374 (comment)

[GrahamMcMynn]

Root cause is fixed, and there is still an Edge issue opened, closing this bug.

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues