SignTool fails to update .nupkg because .nupkg is used by another process
See original GitHub issueAfter updating aspnetcore signtool from 1.0.0-beta.18614.1 to 1.0.0-beta.19057.6, we started getting consistent build failures with this error:
CodeSign.targets(51,5): error : Updating 'C:\b\w\e37dd45d8cd1eaf4\artifacts\\packages\Release\Shipping\Microsoft.AspNetCore.App.3.0.0-preview-19068-0407.nupkg' with signed content failed: 'The process cannot access the file 'C:\b\w\e37dd45d8cd1eaf4\artifacts\\packages\Release\Shipping\Microsoft.AspNetCore.App.3.0.0-preview-19068-0407.nupkg' because it is being used by another process.'
I’ve reverted back to signtool 1.0.0-beta.18614.1 to workaround this, but this is currently blocking us from update to the latest version.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Signing NuGet Packages
Read a detailed guide about the process of designing and creating a NuGet package, including key decision points like files and versioning.
Read more >An error occurred while signing: SignTool.exe not found
This is a simple fix. Open the project you are getting this error on. Click "Project" at the top. Then click " Properties"...
Read more >Signtool file in use error when creating exe in version 18.7
EXE (last step so the installer exe) it says the file is being used by another process. But it is not me. Full...
Read more >SignTool Error: The /p option requires the /f option
Recently, we got error APPX1204: SignTool Error: The /p option requires the /f option in our build for Uwp application.
Read more >Deploying your smart desktop - Finsemble
When generating an update, two nupkg files are generated: full and delta . The full nupkg file isn't used for installation, but can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It must be something our build which is causing strange race conditions. Still investigating on my end. I’ll re-open if I determine conclusively that we need a change to signtool.
Here are two: