Newly added web part not showing up in the web part picker after solution re-deployment

[vishalshitole]

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

• browser version: Latest
• SPFx version: 1.18.2
• Node.js version: 18.19.0

Issue description

We have an SPFx solution (1.14.3.0) that is deployed using the tenant app catalog (not added by default to all sites though). We recently added a new web part in this existing solution, and tried to redeploy the updated version in tenant app catalog. While deploying the new version, we accidently added the duplicate copy of the .sppkg, which caused an error as shown in the below screenshot.

However, we immediately deleted the duplicate package, and redeployed the package with latest version (1.16.0.1). But, it does not appear to be syncing to the sites where the app is previously installed. The newly added web part does not appear in the web part picker on site page.

Is this happening because of the above error? How do we resolve this issue?

Note: This solution is deployed to hundreds of sites with web parts being used on hundreds of site pages.

@AJIXuMuK I saw a similar issue with your comment. Any suggestions for this one would be highly appreciated.

Thanks.

[Ashlesha-MSFT]

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

[Ashlesha-MSFT]

@vishalshitole,
Thanks for sharing the details. A couple of things you might want to check:

Update-SPApp or Update-SPSolution
If you're managing the deployment via PowerShell, it’s worth reviewing the official documentation on Update-SPSolution.

Test with a New GUID (as a last resort)
If all other deployment and sync mechanisms fail (including using Update-PnPApp), you might consider updating the solution’s id in package-solution.json — effectively giving it a new GUID.
This will cause SharePoint to treat it as a new solution, allowing a clean installation and avoiding possible issues from a corrupted or incomplete app state.

[Ashlesha-MSFT]

@vishalshitole,
Just following up to check if there’s been any progress on this. Please let us know if anything is needed to move forward.

[Ashlesha-MSFT]

We are closing this issue for now. If the problem persists, feel free to reopen it or open a new one.