SOLVED

SPFX webpart not added to site after deployment

%3CLINGO-SUB%20id%3D%22lingo-sub-2661775%22%20slang%3D%22en-US%22%3ESPFX%20webpart%20not%20added%20to%20site%20after%20deployment%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2661775%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI%26nbsp%3B%3C%2FSPAN%3Ehave%20developed%20a%20SPFx%20WebPart%20using%20react.%20When%20packaging%20this%20solution%2C%20I%20use%20the%20following%20commands%3A%3C%2FP%3E%3CPRE%3Egulp%20clean%0Agulp%20bundle%20%3CSPAN%20class%3D%22hljs-comment%22%3E--ship%3C%2FSPAN%3E%0Agulp%20%3CSPAN%20class%3D%22hljs-built_in%22%3Epackage%3C%2FSPAN%3E-solution%20%3CSPAN%20class%3D%22hljs-comment%22%3E--ship%3C%2FSPAN%3E%0A%3C%2FPRE%3E%3CP%3EFYI%2C%20I'm%20using%20these%20options%20in%20my%20package-solution.json%20file%3A%3C%2FP%3E%3CPRE%3E%3CSPAN%20class%3D%22hljs-attr%22%3E%22skipFeatureDeployment%22%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%3A%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-keyword%22%3Etrue%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%2C%3C%2FSPAN%3E%0A%3CSPAN%20class%3D%22hljs-attr%22%3E%22includeClientSideAssets%22%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%3A%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-keyword%22%3Etrue%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%2C%3C%2FSPAN%3E%0A%3CSPAN%20class%3D%22hljs-attr%22%3E%22isDomainIsolated%22%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%3A%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-keyword%22%3Etrue%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-punctuation%22%3E%2C%3C%2FSPAN%3E%0A%3C%2FPRE%3E%3CP%3E%3CFONT%20size%3D%222%22%3E%3CEM%3EIt's%20worth%20noting%2C%20I've%20tried%20both%20with%20tenant%20deployment%20(skipFeatureDeployment%20%3D%20true%2Ffalse)%20and%20without%2C%20same%20issue.%26nbsp%3B%20If%20I%20don't%20deploy%20it%20to%20the%20tenant%2C%20adding%20it%20to%20the%20site%20shows%20success%20but%20really%20fails%20behind%20the%20scene%20as%20it's%20no%20longer%20%22added%22%20after%20a%20refresh.%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20successfully%20creates%20my%20.sppkg%20file.%20No%20errors.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20then%20upload%20the%20package%20to%20my%20SharePoint%20sites%20App%20Catalog%20in%20SharePoint%20Online%20(365)%2C%20successfully%2C%20with%20no%20errors%2C%20then%20choose%20deploy%2C%20in%20this%20case%20to%20all%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20app%20in%20the%20catalog%20displays%20as%20enabled%2C%20valid%2C%20deployed%20and%20tenant%20deployed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20the%20app%20does%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ENOT%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eshow%20up%20in%20my%20site%20contents.%20The%20app%20does%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ENOT%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eshow%20up%20in%20%22My%20apps%22%20for%20the%20site.%20The%20app%20does%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3ENOT%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eshow%20up%20in%20the%20WebPart%20picker%20of%20a%20page.%20If%20I%20create%20a%20simple%20helloworld%20app%20scaffolded%20from%20yo%2C%20it%20works%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20there%20is%20something%20about%20this%20app%20it%20does%20NOT%20like.%20Where%20can%20I%20track%20down%20the%20logs%20or%20other%20data%20that%20would%20indicate%20why%20this%20app%20is%20failing%20silently%20and%20giving%20me%20no%20visual%20indication%20there%20is%20a%20problem%20during%20deployment%3F%20It%20may%20also%20be%20worth%20noting%20that%20this%20app%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EWAS%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eworking%20last%20week%20when%20I%20first%20deployed%20it.%20However%2C%20I%20deleted%20the%20app%20from%20the%20catalog%20and%20re-deployed%20several%20times%20testing%20different%20settings.%20Now%20I%20can't%20get%20it%20to%20show%20at%20all.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2661775%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESPFx%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

have developed a SPFx WebPart using react. When packaging this solution, I use the following commands:

gulp clean
gulp bundle --ship
gulp package-solution --ship

FYI, I'm using these options in my package-solution.json file:

"skipFeatureDeployment": true,
"includeClientSideAssets": true,
"isDomainIsolated": true,

It's worth noting, I've tried both with tenant deployment (skipFeatureDeployment = true/false) and without, same issue.  If I don't deploy it to the tenant, adding it to the site shows success but really fails behind the scene as it's no longer "added" after a refresh.

 

This successfully creates my .sppkg file. No errors.

 

I then upload the package to my SharePoint sites App Catalog in SharePoint Online (365), successfully, with no errors, then choose deploy, in this case to all sites.

 

The app in the catalog displays as enabled, valid, deployed and tenant deployed.

 

However, the app does NOT show up in my site contents. The app does NOT show up in "My apps" for the site. The app does NOT show up in the WebPart picker of a page. If I create a simple helloworld app scaffolded from yo, it works as expected.

 

So there is something about this app it does NOT like. Where can I track down the logs or other data that would indicate why this app is failing silently and giving me no visual indication there is a problem during deployment? It may also be worth noting that this app WAS working last week when I first deployed it. However, I deleted the app from the catalog and re-deployed several times testing different settings. Now I can't get it to show at all.

1 Reply
best response confirmed by JasonEades (New Contributor)
Solution
This is some sort of caching issue related to removing/adding the app from the AppCatalog. The only solution I found was to delete the app, then change the guid id in the package-solution.json file, re-deploy. It began showing up again after that.