-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
KNOWN ISSUE: .NET SDK 8.0.200 Installs the Incorrect MAUI Workload Versions #20600
Comments
I'm currently encountering this issue on iOS, specifically when building with the macOS-13 vmImage. The build is failing due to an older version of iOS SDK. When can we expect a resolution for this? I have numerous self-created packages that reference iOS 17.0, while the workload the vm is installing is version 16.4. I don't intend to make extensive changes right now. Hoping for a quick fix here! |
Workaround is not working for me (on MacOS arm64)
I created a folder for each sdk version like this:
From each folder I checked installed workloads Then from
See these
To solve the situation I had to remove and reinstall everything:
then install .NET 8.0.101 +
|
Does anyone know if 8.102 is affected by this bug as well? (I have verified myself that 8.101 works and 8.200 fails badly.) My "workaround" was to uninstall the whole shebang (SDK 8.200, I mean). I expect there will be a fixed 8.201 soon?!? This is pretty severe. |
@Redth is the version deployed by visual studio affected as well? |
This version is not affected. I ran it yesterday successfully. |
@albyrock87's example will work if you ran into this on your local developer machine: #20600 (comment) If you are seeing this on Azure DevOps, you can install 8.0.101 or some 8.0.1xx version for now: - task: UseDotNet@2
inputs:
version: '8.0.101' |
Is this potential fix coming in the near term? I'm trying to figure out if I should just wait for the fix or do the work to revert all of my projects back to 8.0.101. Thanks. |
@SteveBush can you try it now, they just shipped a new 8.0.201 .NET SDK, and it worked for me here: |
@jonathanpeppers Yes, it is fixed. Working fine on Azure DevOps |
I can also confirm that with 8.0.201 one gets proper workload versions again (and the build errors are gone):
|
Hi all - apologies, I'm a bit inexperienced with this, how can implement this workaround? I've got this in the project when i type
I have this in the sdks:
I can't see an global.json file in my maui solution Have run a clean and deleted bin and obj but still it is not compiling with the MauiUIApplication delegate error |
@ssbssb-cmd there is no need for a workaround anymore. The 8.0.201 .NET SDK installs the latest workloads successfully:
File a new issue, if you are having a different problem, thanks! |
With the recent release of the 8.0.200 .NET SDK, there is an issue occurring where installing some workloads (including
maui
) attempts to install an incorrect (older) version of the workload itself. While the workload installation may succeed, subsequently building MAUI apps may fail.This occurs in situations where the SDK was manually installed and workloads installed via command line. Installations through Visual Studio should be unaffected.
We are currently investigating and testing a potential fix and will post an update when we have more to share.
Workaround
You can work around this by installing an older version of .NET SDK (eg: 8.0.101), installing the maui workload in the context of that SDK version, and setting your global.json to use that SDK version as well.
The text was updated successfully, but these errors were encountered: