Solution with New Extension Added - Tenant Wide Extensions List Entry Not Added

[anthonywhite]

Scenario An SPFx solution with one ListViewCommandSet extension is deployed to tenant app catalog. Two ClientSideComponentInstance entries are in the ClientSideInstance.xml file. Two corresponding entries appear in Tenant Wide Extensions List.

An update is made to the solution that adds another ListViewCommandSet extension and a single ClientSideInstance.xml entry. The package-solution.xml version is incremented. The new version is built and deployed by dragging and dropping over the previous version in the app catalog. However no new entry appears in the Tenant Wide Extensions List for the new extension.

Adding the TWE entry manually enables the new extension ok. Deleting the app from the catalog correctly removes all the TWE entries. Adding the solution back in after deleting correctly creates all the TWE entries.

The problem just seems to be with (not) processing an update to ClientSideInstance.xml file?

[ghost]

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

[AJIXuMuK]

Thanks @anthonywhite for bringing this up. We're working on a fix to allow adding new extensions to the ClientSideInstance.xml. To be clear, it will cover the scenario when you add new component in your solution and want to add this component registration to ClientSideInstance.xml. If you want to modify existing entries, or add new registration for existing component, it will not work.

[anthonywhite]

Thanks @AJIXuMuK, I guess more complex scenarios such as you mention can be handled manually 👍

[AJIXuMuK]

@anthonywhite - the roll out should be finished by today.

[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