With .NET 6.0 RC2(6.0.100-rc.2.21469.5) SDK, I can't install Blazor WebAssembly AOT workload.
See original GitHub issueDescribe the bug
This issue may be caused by the Feed, is the Feed signed?
Workload installation failed: One or more errors occurred. (Failed to validate package signing.
Verifying Microsoft.NET.Runtime.WebAssembly.Sdk.Msi.x64.6.0.0-rc.2.21468.3
Signature type: Author
Subject Name: CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
SHA256 hash: AA12DA22A49BCE7D5C1AE64CC1F3D892F150DA76140F210ABD2CBFFCA2C18A27
Valid from: 9/29/2020 5:00:00 PM to 10/5/2023 5:00:00 AM
error: NU3008: The package integrity check failed. The package has changed since it was signed. Try clearing the local http-cache and run nuget operation again.
Package signature validation failed.
To Reproduce
-
Install latest Dev17.0 Preview 5(main-31721.352).
-
Install .NET 6.0 RC2 SDK from: Pipelines - Run 20210919.1-6.0.100-rc.2.21469.5-109627 artifacts (azure.com)
-
Open commandline as administrator, run below command to install AOT workload, but failed.
dotnet workload install wasm-tools
-
Run below command to install the workload and skip the advertising manifests, failed again.
dotnet workload install wasm-tools --skip-manifest-update
Exceptions (if any)
Further technical details
- Include the output of
dotnet --info
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
No results found
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
@mmitche ,@joeloff, using the latest 6.0 RC2 SDK(6.0.100-rc.2.21476.4), and corresponding feed, I can install the wasm-tools successfully now.
Close this issue as fixed