Forum Discussion
Signtool cannot sign msix file produced by dotnet publish
Used dotnet publish to generate a msix package (from Blazor MAUI project). During the process, dotnet has signed the msix file using our EV certificate, but it did not time-stamp it. So we’ve decided...
I have the exact same issue. Have you been able to fix it?
I cannot speak to the specific issue, but most of the time for someone signing MSIX packages for the first time the issue is that the PUBLISHER field of the AppXManifest file inside the package must EXACTLY match the string that is the subject name field of the certificate.