SOLVED

Optional Package Cross Publisher Scenario - different publisher than Base Package

%3CLINGO-SUB%20id%3D%22lingo-sub-1641456%22%20slang%3D%22en-US%22%3EOptional%20Package%20Cross%20Publisher%20Scenario%20-%20different%20publisher%20than%20Base%20Package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1641456%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20stated%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Farchive%2Fblogs%2Fappinstaller%2Fuwpoptionalpackages%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%2C%20Optional%20Packages%20should%20work%20with%20different%20publishers%20that%20the%20Base%20Package's%20one%3A%3C%2FP%3E%3CP%3E%3CEM%3E%22Cross%20Publisher%20Scenarios%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ETaking%20this%20a%20step%20further%20the%20platform%20supports%20the%20ability%20for%20the%20optional%20package%20and%20base%20package%20to%20be%20from%20different%20publishers%20if%20you%20want%20to%20co-develop%20with%20other%20publishers.%20I%20want%20to%20high%20light%20that%20these%20are%20publishers%20that%20you%20trust%20and%20the%20base%20app%20controls%20what%20optional%20packages%20it%20works%20with%20as%20you%20are%20loading%20content%2F%20code%20in%20proc.%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20I'm%20facing%20is%20that%20when%20installing%20an%20Optional%20Package%20with%20a%20different%20publisher%20than%20the%20Base%20Package's%2C%20the%20next%20error%20shows%20up%2C%20even%20though%20the%20Base%20Package%20has%20the%20Optional%20Package%20correctly%20bound%20as%20a%20related%20set%20(no%20application%20inside%2C%20used%20just%20to%20specify%20it's%20publisher)%3A%3CBR%20%2F%3E%3CEM%3E%22A%20main%20app%20package%20is%20required%20to%20install%20this%20optional%20package.%20Install%20the%20main%20package%20first%20and%20try%20again%20(0x80003d12)%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20use%20the%20same%20publisher%2C%20it%20works%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20causing%20this%20issue%20%3F%20How%20can%20I%20use%20different%20publishers%20%3F%20Is%20there%20some%26nbsp%3Bmissing%20documentation%2C%20or%20this%20feature%20is%20not%20supported%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1646305%22%20slang%3D%22en-US%22%3ERe%3A%20Optional%20Package%20Cross%20Publisher%20Scenario%20-%20different%20publisher%20than%20Base%20Package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1646305%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F230350%22%20target%3D%22_blank%22%3E%40Victor%20Vica%3C%2FA%3E%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20will%20need%20to%20specify%20the%20Publisher%20of%20the%20main%20application%20if%20they%20are%20different.%20Like%20so%26nbsp%3B%3CSPAN%3E%26lt%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-name%22%3Euap4%3AMainPackageDependency%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-attr%22%3EName%3C%2FSPAN%3E%3CSPAN%3E%3D%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-string%22%3E%22Main_app%22%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22hljs-attr%22%3EPublisher%3C%2FSPAN%3E%3CSPAN%3E%3D%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-string%22%3E%22CN%3Dxxxxxx%22%3C%2FSPAN%3E%3CSPAN%3E%20%2F%26gt%3B%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENote%20that%20this%20is%20not%20supported%20in%20the%20Store.%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThank%20you%2C%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EDian%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1656839%22%20slang%3D%22en-US%22%3ERe%3A%20Optional%20Package%20Cross%20Publisher%20Scenario%20-%20different%20publisher%20than%20Base%20Package%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1656839%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F144649%22%20target%3D%22_blank%22%3E%40Dian%20Hartono%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20reply.%20Your%20advice%20was%20correct%20and%20it%20works.%20I%20was%20mislead%20by%20the%20Optional%20Package%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FAppInstaller%2FOptionalPackageSample%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Esamples%3C%2FA%3E%20-%26nbsp%3B%3CEM%3E%3CMAINPACKAGEDEPENDENCY%20name%3D%22%26quot%3B29270depappf.AtomicSuite%26quot%3B%22%3E%3C%2FMAINPACKAGEDEPENDENCY%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVictor%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

As stated here, Optional Packages should work with different publishers that the Base Package's one:

"Cross Publisher Scenarios
Taking this a step further the platform supports the ability for the optional package and base package to be from different publishers if you want to co-develop with other publishers. I want to high light that these are publishers that you trust and the base app controls what optional packages it works with as you are loading content/ code in proc."

 

The issue I'm facing is that when installing an Optional Package with a different publisher than the Base Package's, the next error shows up, even though the Base Package has the Optional Package correctly bound as a related set (no application inside, used just to specify it's publisher):
"A main app package is required to install this optional package. Install the main package first and try again (0x80003d12)"

 

If I use the same publisher, it works as expected.

 

What is causing this issue ? How can I use different publishers ? Is there some missing documentation, or this feature is not supported ?

2 Replies
Best Response confirmed by Victor Vica (Occasional Contributor)
Solution

Hi @Victor Vica

You will need to specify the Publisher of the main application if they are different. Like so <uap4:MainPackageDependency Name="Main_app" Publisher="CN=xxxxxx" /> 

 

Note that this is not supported in the Store. 

 

Thank you,

Dian 

 

Hi, @Dian Hartono 

Thanks for your reply. Your advice was correct and it works. I was mislead by the Optional Package samples<uap3:MainPackageDependency Name="29270depappf.AtomicSuite" />

 

Victor