-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: An error occurred signing the manifest. Check that all signature parameters are correct. #47
Comments
Hi, Not that I can think of. Intermittant bugs are notoriously difficult to debug, and I don't actually use signing in any of my builds. I'm relying on the CodeSigning repo to handle certificates. That said, I'm happy to look into it. Is the certificate you're using installed on the server (located by thumbprint) or added as an Azure DevOps secure file? |
Hi,
The certificate is added as an azure devops secure file.
Thanks!
Regards
Marcus
From: Andrew Mansell ***@***.***>
Sent: den 19 augusti 2021 23:59
To: mansellan/clickonce ***@***.***>
Cc: Pettersson, Marcus ***@***.***>; Author ***@***.***>
Subject: Re: [mansellan/clickonce] ERROR: An error occurred signing the manifest. Check that all signature parameters are correct. (#47)
Hi,
Not that I can think of. Intermittant bugs are notoriously difficult to debug, and I don't actually use signing in any of my builds. I'm relying on the CodeSigning repo to handle certificates.
That said, I'm happy to look into it. Is the certificate you're using installed on the server (located by thumbprint) or added as an Azure DevOps secure file?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/mansellan/clickonce/issues/47*issuecomment-902277439__;Iw!!L0Ua0Wts!MsRhqYjaPsosKjLhexlHSHXn9r2oraWm8Ekoduq9vq6VmXCQUxyt4jOuhDMCOM6ivdjW$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AVICXSDONXQ4RBRYH2ET6NTT5V5C7ANCNFSM5CL6DEBA__;!!L0Ua0Wts!MsRhqYjaPsosKjLhexlHSHXn9r2oraWm8Ekoduq9vq6VmXCQUxyt4jOuhDMCOJkKfJbB$>.
Triage notifications on the go with GitHub Mobile for iOS<https://urldefense.com/v3/__https:/apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675__;!!L0Ua0Wts!MsRhqYjaPsosKjLhexlHSHXn9r2oraWm8Ekoduq9vq6VmXCQUxyt4jOuhDMCODHhMm3c$> or Android<https://urldefense.com/v3/__https:/play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email__;!!L0Ua0Wts!MsRhqYjaPsosKjLhexlHSHXn9r2oraWm8Ekoduq9vq6VmXCQUxyt4jOuhDMCOJn0ttLu$>.
|
Just a quick update @Marcus222222. I've not been able to repro this with a self-signed cert, and until now haven't had access to a CA cert. However, my work are just about to purchase a code cert so hopefully I will be able to get to the bottom of this soon. |
Really sorry, I'm going to have to close this as I can't repro it. Since I uploaded our corporate certificate, we've had dozens of builds without seeing this. I can only assume it's something unusual with your environment. If you like, you can remove signing from the ClickOnce task and add an explicit Code Signing task - this task just defers to it. Sorry, and I hope you find a solution. |
We have an issues that is not possible to reproduce.
Once in a while we get an error thrown. "ERROR: An error occurred signing the manifest. Check that all signature parameters are correct"
The thing is that the parameters are correct and the same as the previous build that worked.
Any suggestions ?
Best regards
Marcus Pettersson
The text was updated successfully, but these errors were encountered: