-
Notifications
You must be signed in to change notification settings - Fork 446
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
Mobile workloads are broken in 6.0.401-servicing.22410.12 #14389
Comments
@akoeplinger any ideas |
Hmm no idea. |
@rolfbjarne , were you trying the public build of 401 from the installer home page? Can you try an internal build from dnceng instead? I believe this was fixed as part of this PR: dotnet/sdk#26862. Part of that PR was to fix the workload resolution to correctly use the SDK version rather than the SDK feature band version. That change went in after sdk/installer went internal so it won't be available in the public 401 daily builds, only the internal ones. |
What is the solution here? When pinning 6.0.401 which is installed by default with Visual studio 17.3.5 dotnet workload command does not work. |
@jadenrogers , the above issue is unrelated and was specific to a daily build of the 6.0.4xx branch that didn't work for workloads. Can you provide more details on how the workload commands are failing for you? |
@marcpopMSFT Long story short something went bad and I had errors like the above and couldn't reinstall my way out of it. Completely removed all VS instances and re installed, didn't fix it. I ran these commands and many like it but none ever fixed the problem https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md
Had to reinstall windows and start fresh. Everything working as expected. |
Description
Mobile workloads aren't recognized anymore.
Reproduction Steps
Download the latest 6.0.400 daily:
Decompress it:
Try to install a workload:
Expected behavior
The iOS workload should be installed.
Actual behavior
The iOS workload fails to install.
Regression?
Yes.
It regressed between 6.0.401-servicing.22409.27 and 6.0.401-servicing.22410.12 (in this bump: xamarin/xamarin-macios@8fd5010)
Looks like this is the diff:
https://github.com/dotnet/installer/compare/70e189db5c5c7d32118c4fc911b53c88fadf2c58..6b1b8a424a95f31089a49e814e389f0a41daf743
Known Workarounds
Not a complete workaround (since it still fails), but the iOS workload is recognized at least.
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: