Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested
Additional environment details
- SPFx version: 1.22.2
- Node.js version: 22.18.0
Describe the bug / error
Hello,
We have a SharePoint Framework (SPFx) solution that contains four extensions.
In the package-solution.json, we have defined four features, with one feature per extension.
The initial deployment of the solution to the site collection app catalog works as expected.
However, when we deploy a new version of the solution (by uploading an updated .sppkg file), the deployment fails. The app package reports the following error:
Component ID {id} exists more than once in the current package
As a result, none of the extensions are loaded.
As a workaround, we found that deleting all entries related to this solution from the Client Side Component Manifests list and then redeploying the solution allows the deployment to succeed.
This issue appears to be the same as (or closely related to) the one described here: #3802
Steps to reproduce
- Create a SharePoint Framework (SPFx) solution containing multiple extensions.
- In package-solution.json, define one feature per extension (each feature referencing a single extension).
- Deploy the solution to a site collection app catalog.
✅ Initial deployment completes successfully.
- Add the app to the site (New -> App)
- Increment the solution version in package-solution.json.
- Increment the version number of each feature defined in the same file.
- Rebuild the solution using the following commands:
heft clean
heft build --production
heft package-solution --production
- Upload the newly generated .sppkg file to the same site collection app catalog.
🚫 Deployment fails with the error:
Component ID {id} exists more than once in the current package
Expected behavior
- The solution package should deploy successfully without errors.
- Existing extensions should be updated in place based on their component IDs.
- All extensions should be loaded and executed correctly after deployment.
- Updating the solution and feature version numbers should be sufficient, without requiring any manual cleanup or removal of previously deployed components.
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested
Additional environment details
Describe the bug / error
Hello,
We have a SharePoint Framework (SPFx) solution that contains four extensions.
In the package-solution.json, we have defined four features, with one feature per extension.
The initial deployment of the solution to the site collection app catalog works as expected.
However, when we deploy a new version of the solution (by uploading an updated .sppkg file), the deployment fails. The app package reports the following error:
As a result, none of the extensions are loaded.
As a workaround, we found that deleting all entries related to this solution from the Client Side Component Manifests list and then redeploying the solution allows the deployment to succeed.
This issue appears to be the same as (or closely related to) the one described here: #3802
Steps to reproduce
✅ Initial deployment completes successfully.
🚫 Deployment fails with the error:
Expected behavior