Closed JeffBrownTech closed 4 months ago
It does seem something specific with msxibundle file, I can sign another file in the same directory, so not sure what I'm missing for it. Signing another file was successful using the TrustedSigning PowerShell module.
I believe I have this resolved. In the .csproj file, there are several condition blocks that set different PropertyGroup sections with the current certificate signing process information, such as the Publisher, PackageCertificateKeyFile, thumbprint, etc.
Once I removed these and hard-coded the Publisher name to match the certificate profile in the trusted signing resource, it was able to sign the msixbundle file.
I thought I could avoid this as I included -property:AppxPackageSigningEnabled=false
in the msbuild task in the pipeline, but it seems it was still causing issues.
However, if any one can provide more clarity on the signing process in that it took 23 signing operations to successfully sign one file, does that sound about right?
Hi @JeffBrownTech, could you provide the logs which show 23 signing operations? Is the MSIXBundle the only file that you are signing?
@japarson Thank you for following up, I believe I found why. I'm not a dev and am unfamiliar with msixbundle files. Talking with a developer today, he showed how the msixbundle is basically a zip file with multiple files in it. In this case, the one I was test signing had 23-24 files in, all individually signed. I believe this mystery is solved.
I'm attempting to sign an MSIXBundle file using a self-hosted Windows agent in an Azure DevOps pipeline. Task details:
The task fails with the message below:
I enabled debug output, got some more information but nothing that stood out as to why:
I attempted to also sign using SignTool on my Windows 11 workstation and get this message:
I have diagnostic logging enabled on the trusted signing account to a storage account, but it does not yield any further details. Any assistance or guidance would be helpful as I have not found any thing yet.