-
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
Failed to install maui-windows workload on ARM64 #3764
Comments
I don't believe that's a MAUI issue, but a workload issue: I don't think any of the Xamarin SDKs support Windows on ARM yet, so you can't use the dotnet 6 SDK to build any Xamarin based workload, including MAUI. I also don't believe the Android Emulators run on Windows on ARM either, so even if you did get it to work, it's not worth the headaches, IMO. If you want to test a MAUI app on ARM (Specifically WinUI, since I'm guessing that's what you want to test), you should be able to by doing remote deployment on a x64 computer. |
@drasticactions Could you please suggest more relevant repo for this issue?
But I'm trying to install only "maui-windows". Why does it even install these Android and iOS packages?
I use ARM64-based workstation for common .NET projects, but I'm new in modern desktop development. |
Strangely, the maui-windows and macos workloads install fine on arm64 versions of Ubuntu and Alpine linux. A new maui project can be created but, sadly, can't be built. There are Android SDK-related microsoft packages for x64 variants of win, linux and osx but only osx has arm64 builds for all of them. Specifically, dotnet build fails looking for Microsoft.Android.Sdk.BundleTool. I suspect there are other dependent packages that aren't built for arm64 that it would complain about if an arm64 package for BundleTool suddenly showed up on nuget. Still, it seems like a build targetting oversight more than a real technical limitation so it's a bit frustrating to see but who knows what else would be missing that might not be so easy to fix. |
Verified the issue on windows, it's not repro. |
@okolobaxa ; did you manage to publish to arm64 on x64 dev-machine or is the situation the same? |
This installs alright for me now, if you still have issues, please open a new issue with all the details. Thanks! |
Description
Console output:
PS C:\Users\okolobaxa> dotnet workload install maui-windows
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.sdk.maui.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Updated advertising manifest microsoft.net.sdk.tvos.
Updated advertising manifest microsoft.net.workload.emscripten.
Updated advertising manifest microsoft.net.workload.mono.toolchain.
Downloading microsoft.net.sdk.android.manifest-6.0.100.msi.arm64 (31.0.101-preview.11.117)
Installing Microsoft.NET.Sdk.Android.Manifest-6.0.100.31.0.101-preview.11.117-arm64.msi .... Done
Downloading microsoft.net.sdk.ios.manifest-6.0.100.msi.arm64 (15.0.101-preview.11.551)
Workload installation failed. Rolling back installed packs...
Installing Microsoft.NET.Sdk.Android.Manifest-6.0.100.31.0.101-preview.9.16-arm64.msi .... Done
Downloading microsoft.net.sdk.ios.manifest-6.0.100.msi.arm64 (15.0.101-preview.9.31)
Installation rollback failed: One or more errors occurred. (microsoft.net.sdk.ios.manifest-6.0.100.msi.arm64::15.0.101-preview.9.31 is not found in NuGet feeds https://api.nuget.org/v3/index.json;C:\Program Files (x86)\Microsoft SDKs\NuGetPackages".)
Workload installation failed: One or more errors occurred. (microsoft.net.sdk.ios.manifest-6.0.100.msi.arm64::15.0.101-preview.11.551 is not found in NuGet feeds https://api.nuget.org/v3/index.json;C:\Program Files (x86)\Microsoft SDKs\NuGetPackages".)
Steps to Reproduce
dotnet workload install maui-windows
Version with bug
Preview 10 (current)
Last version that worked well
Unknown/Other
Affected platforms
Windows
Affected platform versions
Windows on ARM64
Did you find any workaround?
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: