Issue falling back to 6.0.300 manifests with 6.0.400 SDK
See original GitHub issueDescribe the bug
I have a pipeline I’m testing here: https://github.com/jonathanpeppers/maui-profiling/pull/17
A MAUI service release went out last week, such as:
- https://www.nuget.org/packages/Microsoft.NET.Sdk.Android.Manifest-6.0.300/32.0.415
- https://www.nuget.org/packages/Microsoft.NET.Sdk.Maui.Manifest-6.0.300/6.0.400
- https://www.nuget.org/packages/Microsoft.NET.Workload.Mono.ToolChain.Manifest-6.0.300/6.0.6
- https://www.nuget.org/packages/Microsoft.NET.Sdk.iOS.Manifest-6.0.400/15.4.414
Note that the iOS team went to 6.0.400, while all the other packs did not.
When I use the 6.0.400-preview.22316.6 .NET SDK, and dotnet workload install maui --verbosity diag
, I see:
Advertising manifest not updated. Manifest package for microsoft.net.sdk.android doesn't exist.
Advertising manifest not updated. Manifest package for microsoft.net.sdk.maui doesn't exist.
Advertising manifest not updated. Manifest package for microsoft.net.workload.mono.toolchain doesn't exist.
Then the actual packs installed are not the latest:
Installing pack Microsoft.Android.Sdk version 32.0.301...
Installing pack Microsoft.Maui.Core.Ref.android version 6.0.312...
Installing pack Microsoft.NETCore.App.Runtime.Mono.android-arm version 6.0.5...
I can workaround the problem using a rollback file, like:
{
"microsoft.net.sdk.android": "32.0.415/6.0.300",
"microsoft.net.sdk.ios": "15.4.414/6.0.400",
"microsoft.net.sdk.maccatalyst": "15.4.414/6.0.400",
"microsoft.net.sdk.macos": "12.3.414/6.0.400",
"microsoft.net.sdk.maui": "6.0.400/6.0.300",
"microsoft.net.sdk.tvos": "15.4.414/6.0.400",
"microsoft.net.workload.mono.toolchain": "6.0.6/6.0.300",
"microsoft.net.workload.emscripten": "6.0.4/6.0.300"
}
To Reproduce
I would try the dotnet-install.sh
script like I’m using here:
Then dotnet workload install maui --verbosity diag
and compare the versions that it prints out.
Further technical details
My example above is running on the AzDO hosted mac pool.
View a full build log at:
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Error Pairing iOS Host - Microsoft Q&A
Hi, I am getting below error when trying to pair iOS host: Workload manifest dependency 'Microsoft.NET.Workload.Emscripten' version '6.0.4' ...
Read more >The imported project "C:\Program Files\dotnet\sdk\1.0.3 ...
My solution to this was to convert the project to an Sdk-type csproj. Check out this answer for tips on how to accomplish...
Read more >Failed to pair to Mac with error "Could not install workload ...
I used WinSCP to connect to my Mac from Windows and copied the folder C:\Program Files\dotnet\sdk-manifests\6.0.300\microsoft.net.workload.
Read more >Download .NET 6.0 (Linux, macOS, and Windows)
NET 6.0 downloads for Linux, macOS, and Windows. .NET is a free, cross-platform, open-source developer platform for building many different types of ...
Read more >SDK Resolver Failure - Net 7 - Net 6
I experienced a similar problem. I uninstalled the 7.0.100-preview.5.22307.18 sdk using add remove programs and then changed the ...
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
Yes, the latest few builds on our release branch:
https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet6/NuGet/Microsoft.NET.Sdk.Android.Manifest-6.0.400/versions/32.0.445 sha.8d5cd7f
If this was the file-based install, I am going to assume then that it was the bug that this PR fixed and it’s now resolved and close it: https://github.com/dotnet/installer/pull/14134 Feel free to reactivate if you don’t believe this is accurate.