-
Notifications
You must be signed in to change notification settings - Fork 258
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 NU1403: Package content hash validation failed #8574
Comments
See the steps in this comment: #7921 (comment) |
Possible duplicate of #7921 |
@rrelyea I can try that, but if this is MS's solution, why is it not documented anywhere (except buried in a GitHub thread)? And how does .NET Core 3 SDK and/or runtime affect the solution? |
Issue moved to NuGet/docs.microsoft.com-nuget #1998 via ZenHub |
Converting this to a docs issue: #7921 (comment) |
The linked issue hasn't solved this for me. |
Correction - the linked issue docs do work for me but not if I use |
In order to try to fix this error seen on the GitHub action: > /home/runner/work/serilog-formatting-log4net/serilog-formatting-log4net/src/Serilog.Formatting.Log4Net.csproj : error NU1403: Package content hash validation failed for Microsoft.NETCore.Platforms.1.1.0. The package is different than the last restore. [/home/runner/work/serilog-formatting-log4net/serilog-formatting-log4net/serilog-formatting-log4net.sln] See NuGet/Home#8574 and https://github.com/NuGet/docs.microsoft.com-nuget/issues/1998
Details about Problem
NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe): dotnet
NuGet version (x.x.x.xxx): 5.3.0.3
dotnet.exe --version (if appropriate): 3.0.100-preview9-014004
VS version (if appropriate):
OS version (i.e. win10 v1607 (14393.321)): win10 v1803 (17134.950)
Worked before? If so, with which NuGet version:
Detailed repro steps so we can see the same problem
Find an existing solution (I'll continue to try to narrow this down)
Add the following to Directory.Build.props (in the solution folder)
EXPECTED: CI resolves all packages successfully, just like it does locally.
ACTUAL: CI generates lots of errors:
The error seems to be due to the fallback folder, so I added the following to
Directory.Build.prop
.No change.
Other suggested things
Verbose Logs
Can include privately
The text was updated successfully, but these errors were encountered: