SOLVED

AppSource Store don't support SPFx solution packages

%3CLINGO-SUB%20id%3D%22lingo-sub-164089%22%20slang%3D%22en-US%22%3EAppSource%20Store%20don't%20support%20SPFx%20solution%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-164089%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I'm%20trying%20to%26nbsp%3Brelease%26nbsp%3Ban%20add-in%20to%20the%20Microsoft%20Store%20(AppSource)%20that%20works%20in%20conjunction%20with%20SharePoint%20Framework%20solution.%20According%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdev.office.com%2Fblogs%2Fcombining-store-add-ins-with-high-trust-permissions%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%26nbsp%3Badjustments%3C%2FA%3E%20in%20the%20Store%20policy%2C%20we%20are%20able%20to%20add%20add-in%20that%20works%26nbsp%3Bin%20conjunction%20with%26nbsp%3B%20other%20add-in%20(usually%20an%20add-in%20with%20full%20trust%20rights)%20%3CSPAN%3Eprovided%26nbsp%3B%3C%2FSPAN%3Eoutside%20from%20the%20Store.%26nbsp%3BMy%20add-in%20was%20rejected%20because%20the%20SPFx%20solution%20package%20is%20not%20classified%20as%20%22SharePoint%20Add-ins%20model%22%20and%20thus%20I'm%20not%20covering%20point%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice%2Fdev%2Fstore%2Fvalidation-policies%23bk_4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E4.18%3C%2FA%3E%20form%20the%20store%20policy.%3C%2FP%3E%0A%3CP%3EMy%20questions%20is%20-%20why%20don't%20you%20change%20this%20point%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice%2Fdev%2Fstore%2Fvalidation-policies%23bk_4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E4.18%20%3C%2FA%3E%26nbsp%3Bto%20allow%20also%20SPFx%20solution%3F%3C%2FP%3E%0A%3CP%3EThis%20will%20unlock%20the%20store%20add-ins%20to%20bring%20customization%20to%20the%20modern%20pages...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1439163%22%20slang%3D%22en-US%22%3ERe%3A%20AppSource%20Store%20don't%20support%20SPFx%20solution%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1439163%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F80744%22%20target%3D%22_blank%22%3E%40Dimcho%20Tsanov%3C%2FA%3E%26nbsp%3B%20i%20have%20same%20question%20and%20wondering%20no%20one%20answered%20this%20even%20now.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1439445%22%20slang%3D%22en-US%22%3ERe%3A%20AppSource%20Store%20don't%20support%20SPFx%20solution%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1439445%22%20slang%3D%22en-US%22%3ESupport%20for%20SPFx%20in%20app%20source%20is%20on%20the%20public%20roadmap%20for%20some%20time.%20Hopefully%20part%20of%20the%20next%20major%20release.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1440443%22%20slang%3D%22en-US%22%3ERe%3A%20AppSource%20Store%20don't%20support%20SPFx%20solution%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1440443%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9907%22%20target%3D%22_blank%22%3E%40Joel%20Rodrigues%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20update%20and%20we%20look%20forward%20to%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EShoaib%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1440535%22%20slang%3D%22en-US%22%3ERe%3A%20AppSource%20Store%20don't%20support%20SPFx%20solution%20packages%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1440535%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9907%22%20target%3D%22_blank%22%3E%40Joel%20Rodrigues%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20one%20more%20question%2C%3C%2FP%3E%3CP%3ENow%20as%20we%20can%20develop%20apps%20for%20teams%20through%20SPFX%2C%20Would%20the%20support%20for%20SPFX%20in%20appsource%20be%20only%20for%20SharePoint%20or%20would%20that%20include%20teams%20as%20well%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EShoaib%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi, I'm trying to release an add-in to the Microsoft Store (AppSource) that works in conjunction with SharePoint Framework solution. According to this adjustments in the Store policy, we are able to add add-in that works in conjunction with  other add-in (usually an add-in with full trust rights) provided outside from the Store. My add-in was rejected because the SPFx solution package is not classified as "SharePoint Add-ins model" and thus I'm not covering point 4.18 form the store policy.

My questions is - why don't you change this point 4.18  to allow also SPFx solution?

This will unlock the store add-ins to bring customization to the modern pages...

4 Replies

@Dimcho Tsanov  i have same question and wondering no one answered this even now.

best response confirmed by Beau Cameron (MVP)
Solution
Support for SPFx in app source is on the public roadmap for some time. Hopefully part of the next major release.

@Joel Rodrigues 

 

Thanks for the update and we look forward to that.

 

Regards,

Shoaib

@Joel Rodrigues 

I have one more question,

Now as we can develop apps for teams through SPFX, Would the support for SPFX in appsource be only for SharePoint or would that include teams as well?

 

 

Regards,

Shoaib