Intermittent NU3004 errors (fixed?)
See original GitHub issueTime to time I see errors like this one in the Arcade CI build:
error NU3004: Package 'vswhere 2.6.7' from source 'https://api.nuget.org/v3/index.json': This repository indicated that all its packages are repository signed; however, this package is unsigned.
Doesn’t make much sense to me as it happens only sometimes… The package is definitely signed.
Failure example: https://dev.azure.com/dnceng/public/_build/results?buildId=172551
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (17 by maintainers)
Top Results From Across the Web
NuGet Error NU3004
This error may happen due to a bug when using multiple NuGet clients (see NuGet/Home#7997). Please upgrade to nuget.exe 5.1.0 or newer, ...
Read more >HTTP cache: RepositoryResources resource is not ...
Although RepositorySignatures resources are versioned, the cached content is not versioned in NuGet's HTTP cache. This means if a 5.0 client ...
Read more >Dotnet restore error "error NU3004: The package is not ...
1 Answer 1 ... I had the same issue. For me It's fixed by adding Nuget.exe and nuget.config(https://learn.microsoft.com/en-us/nuget/reference/ ...
Read more >Error "NU3034 This package is signed but not by a trusted ...
Running nuget trusted-signers list showed I had one trusted signer by the name of "NuGet Test Developer".
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
@riarenas yes I’ll get someone on this this morning.
@tmat, there are 2 known scenarios where you might get this error erroneously: