Command set extension not visible in list when in Teams web or desktop app

[andreasomayrat]

Target SharePoint environment

SharePoint Online

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

💥 SharePoint Framework

Developer environment

None

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: Microsoft Edge - Version 133.0.3065.82 (Official build) (64-bit)
• SPFx version: 1.17.4
• Node.js version: 16.13.2

Describe the bug / error

Our solution uses a command set extension (Context Menu only) to handle certain metadata on a list item. In that SharePoint, this solution works flawlessly. In a Teams Tab (web or desktop app) however, no command set extensions are visible at all, only the default right click options. We have two different solutions that are both command set extensions, and they work fine in SharePoint but not in Teams Tabs.

In the Teams Tab, I have tried using the SharePoint app, the SharePoint Pages app, and the Lists app but the command set extension does not work in any of them.

If I go to the Teams Tab list in the web, I get these error logs when it tries to load our command set extension:

listview-host-assembly_sv-se_<random_number>.js:128 Refused to load the script 'https://.sharepoint.com/sites/AppCatalog/ClientSideAssets//-command-set_<random_number>.js' because it violates the following Content Security Policy directive: "script-src https://res-1.cdn.office.net https://contentstorage.osi.office.net https://swx.cdn.skype.com https://res.delve.office.com https://lpcres.delve.office.com https://widget.uservoice.com https://by2.uservoice.com https://www.bing.com/api/maps/ https://www.bing.com/rms/ https://fabriciss.azureedge.net https://publiccdn.sharepointonline.com https://ajax.aspnetcdn.com https://res-1.cdn.office.net https://res-1.cdn.office.net https://res-2.cdn.office.net https://webshell.suite.office.com https://amcdn.msftauth.net *.cdn.office.net *.fluidpreview.office.net https://res-1.cdn.office.net https://teams.microsoft.com https://js.monitor.azure.com https://r4.res.office365.com https://c1-excel-15.cdn.office.net https://c1-onenote-15.cdn.office.net https://c1-powerpoint-15.cdn.office.net https://c1-visio-15.cdn.office.net https://c1-word-view-15.cdn.office.net https://loki.delve.office.com https://res.cdn.office.net/midgard/ https://substrate.office.com 'unsafe-eval' 'nonce-qt8gqjoiycq'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

listview-host-assembly_sv-se_<random_number>.js:128 Refused to load the script 'https://.sharepoint.com/sites/AppCatalog/ClientSideAssets//CommandSetStrings_en-us_<random_number>.js' because it violates the following Content Security Policy directive: "script-src https://res-1.cdn.office.net https://contentstorage.osi.office.net https://swx.cdn.skype.com https://res.delve.office.com https://lpcres.delve.office.com https://widget.uservoice.com https://by2.uservoice.com https://www.bing.com/api/maps/ https://www.bing.com/rms/ https://fabriciss.azureedge.net https://publiccdn.sharepointonline.com https://ajax.aspnetcdn.com https://res-1.cdn.office.net https://res-1.cdn.office.net https://res-2.cdn.office.net https://webshell.suite.office.com https://amcdn.msftauth.net *.cdn.office.net *.fluidpreview.office.net https://res-1.cdn.office.net https://teams.microsoft.com https://js.monitor.azure.com https://r4.res.office365.com https://c1-excel-15.cdn.office.net https://c1-onenote-15.cdn.office.net https://c1-powerpoint-15.cdn.office.net https://c1-visio-15.cdn.office.net https://c1-word-view-15.cdn.office.net https://loki.delve.office.com https://res.cdn.office.net/midgard/ https://substrate.office.com 'unsafe-eval' 'nonce-qt8gqjoiycq'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

VM59570 FileBrowser.aspx:1 Refused to load the script 'https://.sharepoint.com/sites/AppCatalog/ClientSideAssets//CommandSetStrings_en-us_<random_number>.js' because it violates the following Content Security Policy directive: "script-src https://res-1.cdn.office.net https://contentstorage.osi.office.net https://swx.cdn.skype.com https://res.delve.office.com https://lpcres.delve.office.com https://widget.uservoice.com https://by2.uservoice.com https://www.bing.com/api/maps/ https://www.bing.com/rms/ https://fabriciss.azureedge.net https://publiccdn.sharepointonline.com https://ajax.aspnetcdn.com https://res-1.cdn.office.net https://res-1.cdn.office.net https://res-2.cdn.office.net https://webshell.suite.office.com https://amcdn.msftauth.net *.cdn.office.net *.fluidpreview.office.net https://res-1.cdn.office.net https://teams.microsoft.com https://js.monitor.azure.com https://r4.res.office365.com https://c1-excel-15.cdn.office.net https://c1-onenote-15.cdn.office.net https://c1-powerpoint-15.cdn.office.net https://c1-visio-15.cdn.office.net https://c1-word-view-15.cdn.office.net https://loki.delve.office.com https://res.cdn.office.net/midgard/ https://substrate.office.com 'unsafe-eval' 'nonce-qt8gqjoiycq'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Steps to reproduce

1. Install a command set extension solution in the app catalog
2. Configure a list in SharePoint to use the command set extension
3. Set that list as a tab in a Teams channel
4. Right click an item in the list in Teams. The default options are available but not the command set extension

Expected behavior

When I navigate to a Teams tab that displays a SharePoint list, I expect my command set extension to be visible in the context menu

[Ashlesha-MSFT]

Hello @andreasomayrat,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[andreasomayrat]

I found a workaround. If I add a my list via the List webpart to a site page, and then add that site page as a Teams Tab, my command set extension seems to work fine.

[Ashlesha-MSFT]

@andreasomayrat,
We were able to reproduce the issue, and we are investigating it. We will log this as a bug, and our engineering team will look into it.