Repository navigation
Extension information not added to Tenant wide extensions #10214
Description
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
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
SPFx version: v1.18
Issue description
I have a solution containing 2 webparts and an extension. For some reason the extension isn't deployed tenant wide, the entry doesn't get added to the tenant wide extensions list (/sites/AppCatalog/Lists/TenantWideExtensions).
I don't see anything wrong with my configuration.
/sharepoint/assets/ClientSideInstance.xml:
<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
<ClientSideComponentInstance
Title="Productname"
Location="ClientSideExtension.ListViewCommandSet"
ComponentId="GUID from extension's manifest"
Properties=""
ListTemplateId="101">
</ClientSideComponentInstance>
</Elements>config/package-solution.json:
{
"$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
"solution": {
"name": "productname",
"id": "GUID",
"version": "3.1.3.0",
"includeClientSideAssets": true,
"skipFeatureDeployment": true,
"isDomainIsolated": false,
"features": [
{
"title": "Productname",
"description": "Productname",
"id": "GUID",
"version": "3.0.0.0",
"assets": {
"elementManifests": [
"ClientSideInstance.xml"
]
}
}
]
},
"paths": {
"zippedPackage": "solution/productname.sppkg"
}
}I do see the ClientSideInstance.xml included in the resulting sppkg.
I do have to "deploy to all sites" option checked when updating the extension.
But why doesn't it get applied? Am I missing something?
Activity
Ashlesha-MSFT commentedon Apr 29, 2025
Hello Roel (@RoelVB),
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Amey-MSFT commentedon May 5, 2025
Hello Roel (@RoelVB),
We’ve have reached out to the engineering team for a definitive answer and will share their response once available.
RoelVB commentedon Jun 27, 2025
Amey-MSFT
Is there any progress on this. I there something I can check/test?
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.