Description

I attempted to upgrade 3 web parts from v1.11 to 1.14 recently.

In all 3 cases, after I installed the v1.14 version into the app catalog, I could add to a site through site contents but could not add it to a page.

NOTE: Two were fairly complex real projects, one was a Hello World just to make sure it was not my projects.

Steps to reproduce

I took note of each step and have a lot of screenshots so I will do all that in a reply to keep it clean.

I also documented the original 1.11 hello-world and tracked the upgrade to v1.14 in this repo:
https://github.com/mikezimm/native1.11

This branch was the initial v1.11 build

https://github.com/mikezimm/native1.11/tree/v1.14-cli-upgrade-suggestions

• It includes the upgrade report md and also code tour.
• I tested via gulp and then deployed the package.
• I added it to a site and page to confirm it worked as expected.

This branch was the same web part upgraded to v1.14 using the CLI:

https://github.com/mikezimm/native1.11/tree/v1.14-execute-cli-upgrade-instructions

• I tested via gulp and then deployed the package.
• I was never able to add it to a page though because it was not in the toolbox after installing on the page.

Expected results

In the past, whenever I upgraded web parts (mostly just internal versions, not SPFx versions), I just:

added to app catalog
waited a couple hours
web parts were automatically updated wherever I went.

There was never any issues or hassles, was very dependable

I just want to know what I did wrong or what I can do to resolve the issue.

Actual results

Sites where the web part was previously installed seemed to upgrade ok.

On new sites, I was able to add the app to Site Contents, but could not add it to a page or SPA.

Diagnostics

No response

CLI for Microsoft 365 version

"v5.7.0"

nodejs version

v14.17.6

Operating system (environment)

Windows

Shell

cmd

cli doctor

No response

Additional Info

I will attach my install/upgrade notes and screenshots in a reply.

Fix

• We should add a separate feature for each web part in the project > right now we only add one
• The ID of the feature should match the component ID of the web part it provisions > right now we use a random ID which leads to errors