ListViewCommandSet Extension not loading when navigating from Start page after clearing cache

[HussainRuhullah]

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Linux

What browser(s) / client(s) have you tested

• 💥 Internet Explorer
• 💥 Microsoft Edge
• 💥 Google Chrome
• 💥 FireFox
• 💥 Safari
• mobile (iOS/iPadOS)
• mobile (Android)
• not applicable
• other (enter in the "Additional environment details" area below)

Additional environment details

• browser version
• SPFx version
• Node.js version
• etc

Describe the bug / error

The issue was previously reported and closed, but it has resurfaced again. I have included links to the previous issues for reference.

Some of our 365 tenants are experiencing an issue where the command buttons are not loading.
This issue only occurs after clearing the cache, and only if a user doesn't directly navigate to the list where the button is.

As a result, ListViewCommandSet extensions are unusable and hamper the functionality of our product.

As mentioned by @andrewconnell it's a platform fix (ie: server-side).

Previous issues:
#6611
#6116
#5704

Steps to reproduce

1. Create a Command Set Extension project with Yeoman SharePoint Generator $yo @microsoft/sharepoint
2. Bundle and upload the button to app catalog
3. clear browser cache and login to your SharePoint Tenant
   example: https://yourTenant.sharepoint.com/sites/hruh-test
4. Navigate to List where the Extension is Installed using the navigation tree
   example: https://yourTenant.sharepoint.com/sites/hruh-test/myList/Forms/AllItems.aspx
5. The extension does NOT load on first page load
6. Refresh the page to see the Extension.

Expected behavior

Command Button should be visible on document library without refresh.

[ghost]

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

[nick-pape]

This appears to be a duplicate of: #9180

Please follow this ticket. Thank you.

[HussainRuhullah]

@nick-pape Thank you for your fast response.
However, the link provided is to this issue.

As mentioned in the description, this problem was solved by Microsoft in the past, but it is occurring again now.
That is why I have opened this issue with exact steps to reproduce it, as the steps to produce the issue are not as clear in other tickets.

I appreciate your help and would be grateful if you could provide any guidance or suggestions on how to resolve this issue.

[AJIXuMuK]

@HussainRuhullah - correct dupe link is #9166

[ghost]

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