Jan 06 2021 08:48 AM - edited Jan 06 2021 08:50 AM
I filed a feedback hub issue on the failure attaching both the manifest file and log from the attempt. This post provides additional information that might be helpful to the team.
I have now verified that I correctly surmised the issue by manipulating the manifest in the sequence editor prior to saving the package. These results show that there are two issues:
Specifically, I found that I could edit the manifest inside the packaging tool, prior to saving the package, and the package saves successfully. The changes made were simply to change the uap10 prefix to uap3 on the elements for that protocol handler.
Jan 08 2021 11:00 AM
I believe this is related to what was described in WinSCP fails both manually and automated on W10 20H2 with latest tool build - Microsoft Tech Communi...
As you said the tool used the uap10 prefix instead of uap3 unnecesarily. Then, it created an <uap10:Protocol> element that contained a <uap:DisplayName> instead of <uap10:DisplayName> causing MakeAppx to reject it.
Both issues should be fixed in the latest Insider build of the tool (1.2020.1219.0). I.e., it should use uap3:Protocol in this case and uap10 only when actually needed (e.g. length >= 40), and when it does, the element has the appropriate children.
Jan 08 2021 11:57 AM
@Chacon Ha! I forgot that I'd already figured that out.
Glad to hear the newer version of the packaging tool does this correctly now, but guess what? We didn't know there was a newer version. Why? Because (as far as I know) there was no announcement of it in the community portal. As the VM used for the packaging tool is constantly reverted to a snapshot it never gets updated from the store - we have to have notice somehow.