SharePoint 2016 App Catalog Error when uploading spfx package

%3CLINGO-SUB%20id%3D%22lingo-sub-474986%22%20slang%3D%22en-US%22%3ESharePoint%202016%20App%20Catalog%20Error%20when%20uploading%20spfx%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-474986%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20set%20up%20an%20environment%20with%20SharePoint%202016%20on%20premises%20and%20installed%20cumulative%20updates%20of%20August%202018.%20We%20want%20to%20deploy%20a%20custom%20SPFX%20component%2C%20but%20we%20encounter%20a%20problem%20when%20we%20try%20to%20upload%20our%20package%20to%20the%20appcatalog.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20help%20us%20fix%20this%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20390px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109603i7B592E69A93269B1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%221.png%22%20title%3D%221.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E*In%20our%20AppManifest.xml%20the%20%E2%80%98IsClientSideSolution%E2%80%99%20attribute%20is%20declared%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481083%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%202016%20App%20Catalog%20Error%20when%20uploading%20spfx%20package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481083%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F323251%22%20target%3D%22_blank%22%3E%40Joanna_T%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20the%20versions%20of%20the%20SPFx%20you%20use%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20you%20are%20planning%20to%20use%20the%20same%20client-side%20web%20parts%20in%20both%20SharePoint%202016%20and%20in%20SharePoint%20Online%2C%20you%20need%20to%20use%20the%20SharePoint%20Framework%20v1.1.0%20as%20your%20baseline%20version%20to%20ensure%20that%20the%20web%20part%20works%20in%20both%20environments.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fspfx%2Fsharepoint-2016-support%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsharepoint%2Fdev%2Fspfx%2Fsharepoint-2016-support%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20choose%20it%20from%20the%20yeoman%20scaffold%20tool%20that%20you%20only%20want%20to%20use%20the%20on-premise%20or%20both%20types%20of%20SharePoint%2C%20but%20then%20the%20version%20is%20not%20higher%20than%201.1%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20643px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109923i9889B211D756EE6C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22versionSP.png%22%20title%3D%22versionSP.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThen%20in%20your%20package.json%20you%20can%20find%20the%20package%20version%3A%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20643px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F109924iDCB0417A098EC05D%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22packageversions.png%22%20title%3D%22packageversions.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hello,

 

We've set up an environment with SharePoint 2016 on premises and installed cumulative updates of August 2018. We want to deploy a custom SPFX component, but we encounter a problem when we try to upload our package to the appcatalog.

 

Can you please help us fix this?

1.png

*In our AppManifest.xml the ‘IsClientSideSolution’ attribute is declared

 

4 Replies
Highlighted

@Joanna_T 

Hello,

 

What is the versions of the SPFx you use? 

If you are planning to use the same client-side web parts in both SharePoint 2016 and in SharePoint Online, you need to use the SharePoint Framework v1.1.0 as your baseline version to ensure that the web part works in both environments.

https://docs.microsoft.com/en-us/sharepoint/dev/spfx/sharepoint-2016-support

 

You can choose it from the yeoman scaffold tool that you only want to use the on-premise or both types of SharePoint, but then the version is not higher than 1.1

versionSP.png

Then in your package.json you can find the package version:
packageversions.png

Highlighted

 

 

@Jeroen Branders 

Hi and  thank you for your answer.

You are correct and we use SharePoint Framework v1.1.0. See picture

1.jpg

2.png

Do you think it would be  good choice to install SharePoint 2016 Feature Pack 2?

 

 

 

Highlighted
Yes, you must installed it will you use SPFx on SharePoint 2016
Highlighted

@Jeroen BrandersHi,

We installed the SharePoint October 2018 cumulative update and now it works. 

 

Thank you for your help.