question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build failing because of Signtool Error

See original GitHub issue
##[error].packages\microsoft.dotnet.arcade.sdk\1.0.0-beta.19303.8\tools\Tools.proj(0,0): error NU3027: Package 'Microsoft.DotNet.SignTool 1.0.0-beta.19303.8' from source 'https://dotnetfeed.blob.core.windows.net/arcade-validation/index.json': The signature should be timestamped to enable long-term signature validity after the certificate has expired.

https://dev.azure.com/dnceng/internal/_build/results?buildId=210368&_a=summary

/cc @dotnet/wpf-developers /cc @mmitche

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:45 (45 by maintainers)

github_iconTop GitHub Comments

1reaction
JohnTortugocommented, Jun 13, 2019

@JohnTortugo, in your case when two packages were produced, I’m assuming that they happened on different build-definitions? If so, I think that would explain the problem…

Yes, different build definitions.

0reactions
mmitchecommented, Jun 14, 2019

My understanding (fuzzy!) is that what happens is:

  • The first build starts, gets assigned the default build number 20190613.1
  • The first build runs updatebuildnumber, changes to 16.3.0-preview.20190613.1
  • The second build starts, gets assigned a default build number–but because 20190613.1 is no longer taken, it gets 20190613.1 again
  • Second build updates version number to the same as the first build 😦

I think this could be gotten around with a counter, if we changed the initial assignment of “OfficialBuildId” that gets passed into the Arcade build: https://github.com/dotnet/arcade/blob/ff0f47189f7d8a8b4ad353e37f3fc34aaa3090df/azure-pipelines.yml#L75

That sounds like more an AzDO issue than anything else. We should follow up with them I think.

Read more comments on GitHub >

github_iconTop Results From Across the Web

PostBuild Event fails in Visual Studio after SignTool.exe error
We have a project in Visual Studio 2010 that runs a batch file in the post-build event. That batch calls to signtool.exe from...
Read more >
Known issues and troubleshooting with SignTool - MSIX
This article describes known issues and troubleshooting tips for Sign Tool.
Read more >
SignTool error on build - Developer Community
The issue seems to have been an outdated certificate inherited from the previous build. After disabling the signing from from the project ...
Read more >
SignTool error while trying to build our exe
Re: SignTool error while trying to build our exe​​ In your case it looks like the problem is with the Temp folder. Can...
Read more >
Error Signing Build
When building get the following errors in the build log: SignTool Error: This file format cannot be signed because it is not recognized....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found