Workload ID maui-android is not recognized #38171
Labels
Milestone
Comments
|
dotnet workload install maui |
dotnet-issue-labeler
bot
added
Area-Workloads
untriaged
|
How did you install the SDK? What's in the dotnet/sdk-manifests folder? Seems like a bad install. |
First i used snap-store's NET8 SDK package for installation, but the resulting read-only directory where it's binaries are put in prohibits further dotnet workload installations. So i went on fiddling around as documented in #18933 but in the end i wasn't able to get the maui-android workload to run with NET8. So i completely purged all dotnet artifacts particularly to beware of the dreaded package-mixups documented in the official microsoft-learn article and reinstalled it according the official docs for ubuntu 23.10 where i decided to stay on the official canonical package repo (instead of microsofts provided one for easier future upgrades). Proofing myself everything worked as expected i newed-up a blazor projected utilizing dotnet tool's provided template. For completeness i'd like to mention since this is a new setup i also went on installing the azure CLI, but this time - lacking any other options - choosing the microsoft package repo for ubuntu jammy. |
|
for further details according the |
|
further details about my dotnet setup: |
|
@marcpopMSFT, as you requested I've listed some details about my setup. Have you any ideas what's going on here? I find it very suspicious that a |
|
The sdk-manifests folder is missing all of the maui manifests which is why the workload is unrecognized and can't be installed. Including @rbhanda @MichaelSimons @baronfel who might know about the snap install and jammy installs to know if those are incomplete wrt maui. |
|
any way - @marcpopMSFT thank you for taking the time and looking at it. |
|
Hey, i have the exact same problem :) |
|
@ndr0n : |
|
I have the same issue with arch linux |
|
I had this same issue on Arch after installing dotnet-sdk 8.0.101 with pacman. I fixed this by downloading dotnet via the install scripts (https://dotnet.microsoft.com/en-us/download/dotnet/scripts) and copying the sdk-manifests from "~/.dotnet/sdk-manifests/8.0.100" to "/usr/share/dotnet/sdk-manifests/8.0.100". Afterwards you are able to install maui-android. |
|
@PartedLine thx for sharing; But doing it this way puts us back in the pre-packagemanager era where you'll have to fiddle around managing all the sdk and tooling dependencies by your self. I'd say arguable for a not officially supported distro but not the support you might expect from an officially supported distro. |
|
I have the same problem on ArchLinux. Took a look at arch dotnet-sdk package source code and as far as I can see there is no custom logic there around sdk-manifests. It just grubs the official sdk sources from dotnet/dotnet repo, builds it and copies |
|
is android not supported on dotnet 8.0 arm Ubuntu?
Workload ID Descriptionaspire .NET Aspire SDK (Preview)
|
I have the same with arch. Can you solve that now? |
|
The common thread here is that all of these distributions of the .NET SDK are build using source-build. Source-Build SDKs do not have all of the same workloads as MIcrosoft-authored SDKs. You can read more about this in dotnet/source-build#3242. This is something that I think we will need to address soon. |
|
In the meantime, if you need MAUI workloads I'd suggest using the dotnet-install scripts to install a 'local install' of the Microsoft SDK and use that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
analogous to dotnet/maui#3099 we again get "Workload ID maui-android is not recognized." when running:
interestingly the MAUI workload is not even listed when doing:
my setup:
Steps to Reproduce
No response
Link to public reproduction project repository
No response
Version with bug
8.0.6
Is this a regression from previous behavior?
Yes, this used to work in .NET MAUI
Last version that worked well
Unknown/Other
Affected platforms
I was not able test on other platforms
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: