SOLVED

Build 1105 issues

%3CLINGO-SUB%20id%3D%22lingo-sub-2971888%22%20slang%3D%22en-US%22%3EBuild%201105%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2971888%22%20slang%3D%22en-US%22%3E%3CP%3EInitially%2C%20we%20tried%20to%20use%20the%20October%20release%20and%20experienced%20the%20%22package%20editor%22%20issue.%26nbsp%3B%20We%20found%20that%20we%20didn't%20even%20have%20to%20go%20into%20the%20package%20editor%20to%20experience%20the%20issue%20when%20saving%20off%20the%20package.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20upgraded%20to%20the%20November%20release%20(1.0.2021.1105)%20and%20while%20that%20problem%20went%20away%2C%20we%20ran%20into%20another%20blocking%20bug.%26nbsp%3B%20The%20first%20application%20we%20tried%20(UltraEdit)%2C%20failed%20on%20MakeAppx%20build.%26nbsp%3B%20The%20log%20file%20indicated%20that%20the%20issue%20was%20a%20duplicate%20COM%20GUID%20in%20the%20AppXManifest%20file.%26nbsp%3B%20There%20indeed%20were%20two%20Application%20Extensions%20in%20an%20Application%20that%20were%20both%20COM%20Server%20%2F%20SurrogateServer%20using%20the%20same%20com%20clsid%20guid.%26nbsp%3B%20Manually%20editing%20these%20to%20merge%20the%20entries%20allowed%20us%20to%20have%20the%20manifest%20pass%20validation%20on%20the%20way%20back%20into%20the%20editor%2C%20but%20building%20the%20package%20still%20failed%20(with%20yet%20a%20different%20symptom).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20will%20be%20unable%20at%20this%20time%20to%20reproduce%20in%20order%20to%20submit%20via%20feeedback%20hub%2C%20as%20we%20are%20running%20a%20training%20class%20and%20I%20have%20rebuilt%20a%20bunch%20of%20VMs%20to%20go%20back%20to%20the%20709%20build.%26nbsp%3B%20But%20clearly%20there%20are%20issues%20with%201105%20that%20need%20addressing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2973469%22%20slang%3D%22en-US%22%3ERe%3A%20Build%201105%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2973469%22%20slang%3D%22en-US%22%3EHappy%20to%20look%20into%20this%20further%20if%20you%20can%20submit%20an%20item%20after%20the%20class%20to%20help%20us%20better%20understand%20the%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2997710%22%20slang%3D%22en-US%22%3ERe%3A%20Build%201105%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2997710%22%20slang%3D%22en-US%22%3EI%20was%20also%20able%20to%20find%20an%20error.%3CBR%20%2F%3E%22Process%20MakeAppx.exe%20failed%20with%20exit%20code%201%22%20with%20version%20%221.2021.1105.0%22.%3CBR%20%2F%3EUnfortunately%20I%20don't%20have%20the%20source%20for%20the%20709%20build%20anymore.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3073384%22%20slang%3D%22en-US%22%3ERe%3A%20Build%201105%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3073384%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73899%22%20target%3D%22_blank%22%3E%40John%20Vintzel%3C%2FA%3E%26nbsp%3B%20I%20am%20happy%20to%20report%20that%20the%202022.110%20build%20resolves%20this%20issue!%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

Initially, we tried to use the October release and experienced the "package editor" issue.  We found that we didn't even have to go into the package editor to experience the issue when saving off the package.

 

We upgraded to the November release (1.0.2021.1105) and while that problem went away, we ran into another blocking bug.  The first application we tried (UltraEdit), failed on MakeAppx build.  The log file indicated that the issue was a duplicate COM GUID in the AppXManifest file.  There indeed were two Application Extensions in an Application that were both COM Server / SurrogateServer using the same com clsid guid.  Manually editing these to merge the entries allowed us to have the manifest pass validation on the way back into the editor, but building the package still failed (with yet a different symptom). 

 

I will be unable at this time to reproduce in order to submit via feeedback hub, as we are running a training class and I have rebuilt a bunch of VMs to go back to the 709 build.  But clearly there are issues with 1105 that need addressing.

 

 

 

3 Replies
Happy to look into this further if you can submit an item after the class to help us better understand the issue.
I was also able to find an error.
"Process MakeAppx.exe failed with exit code 1" with version "1.2021.1105.0".
Unfortunately I don't have the source for the 709 build anymore.
best response confirmed by TIMOTHY MANGAN (MVP)
Solution

@John Vintzel  I am happy to report that the 2022.110 build resolves this issue!