-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Could not find workload 'ios' extended by workload 'maui-ios' in manifest 'microsoft.net.sdk.maui' #20686
Comments
Thanks for the issue report @kimbirkelund! This issue appears to be a problem with Visual Studio, so we ask that you use the VS feedback tool to report the issue. That way it will get to the routed to the team that owns this experience in VS. If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks.
|
Pair To Mac is a Visual Studio feature and not maintained in this repo by this team, could you please file this to VSFeedback? |
I get the same error trying to restore the workload from command line, so it doesn't really appear to be Visual Studio related. It seems more to be fallout from the recent 8.0.200/201 kafuffle. |
This might be related to #20600 |
It appears I spoke to soon. Downgrading Visual Studio to 17.8.6 allowed me to connect and build. I'll move the issue to VS feedback. |
same on VS Version 17.10.0 Preview 1.0 🙄 |
I have a new computer with a fresh install of 17.9.0. I haven't found a way to downgrade to 17.8.6. It's a mystery how this could pass the test by Microsoft? Any solution? |
in that regard MAUI as a whole is a complete mystery |
Painful |
I created an issue on VS Feedback for this: https://developercommunity.visualstudio.com/t/Unable-to-install-MAUI-workload-on-Mac-u/10595252 |
This is still a problem in 17.9.1. |
Uninstalling and reinstalling .net maui workloads and .net 8.0 runtime via vs installer helps me deal with this problem. |
This issue is specifically related to pair-to-mac which handles installing all these components for you (on the mac that is). |
The experience of developing maui using mac's VS was particularly poor, so I chosed pair to mac.
I will try it after get off work,thanks. |
I also have the same problem with the latest VS 17.9.1. Please any workaround or solution without downgrading? |
I've switched to using Live Share and VNC for now :-( |
The same issue |
This is embarrassing. |
@kimbirkelund Could you please reply to the VS Feedback and provide the details, I think no one is aware of the actual issue that is going on. |
just for reference - a workaround was posted in the VS Ticket discussion
|
Got the same problem on 17.9.0 |
I have the same issue on 17.9.3 |
17.9.3 Could not install workload 'ios'. Details: Unhandled exception: Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: Could not find workload 'ios' extended by workload 'maui-ios' in manifest 'microsoft.net.sdk.maui' [/Users/rnd/Library/Caches/Xamarin/XMA/SDKs/dotnet/sdk-manifests/8.0.100/microsoft.net.sdk.maui/8.0.3/WorkloadManifest.json] |
Updated to VS 2022 version 17.9.3 and I am still unable to connect to mac: Could not install workload 'ios'. Details: Unhandled exception: Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadManifestCompositionException: Could not find workload 'ios' extended by workload 'maui-ios' in manifest 'microsoft.net.sdk.maui' [/Users/developer/Library/Caches/Xamarin/XMA/SDKs/dotnet/sdk-manifests/8.0.100/microsoft.net.sdk.maui/8.0.3/WorkloadManifest.json] |
Same issue as MohammedBen reported above. |
Microsoft have said they're going to ship a Service Release to VS 2022 17.9.x to fix the pairing issue: https://developercommunity.visualstudio.com/t/Unable-to-install-MAUI-workload-on-Mac-u/10595252#T-N10612988-N10617181 - I asked that question because fixing it in a preview release was fine, but since this was a fairly impactful production incident with a workaround, but a non intuitive one (especially for new starters) it seemed to me it needed a more urgent fix and it appears that is what is happening. To be fair to Microsoft on the Xcode 15.3 compatibility - they have clearly posted (as pinned issues) on both the .NET MAUI and .NET for iOS Repos that Xcode 15.3 is out but that they need to release compatible versions and so to keep using Xcode 15.2 until they state otherwise: #21057 and dotnet/macios#20257 |
Is it just me or this seems like a regular thing for Microsoft these days, just release even if full of bugs/compatibility issues. Whatever happen to build, TEST, then release. |
I have issues with Azure AD B2C login only on physical device in Release mode. I upgraded Visual Studio only to see if there was some build related issue. Everything works fine in Simulator with Release mode. Pairing issue was resolved by by downgrading to Xcode 15.2 and upgrading to Preview 2 for Visual Studio. I'm still getting messaging and client disconnected exceptions. |
@erossini Things I have tried when I get this that usually work for me, in this order:
|
This work around worked great for me: |
This problem does not appear to have been corrected in 17.9.5. Will we have to wait for 17.10 or will it be corrected in the 17.9 train? |
This is still a problem in 17.9.5 |
We're now effectively two years after MAUI was released, and these are STILL the bugs we deal with on a daily basis to even get development up and running. Pure insanity. How any of us are so engrained in the .NET ecosystem to continue putting up with this is puzzling - Stockholm syndrome at its finest! This is a problem for me as well in 17.9.5. |
There is a FIX for this bug but it hasn't been released yet though. Use the work around. |
It was fixed in 17.9.4, I made prod MAUI build. |
If you installed and have XCode 15.3 then that breaks it. |
I think so?! I have updated to 17.9.5 and its broken ... |
It's shameful that Microsoft considers an issue fixed if the fix is only in preview software. Most of us actually using these tools to make our living are doing so in production environments, and of course we are not using preview software in production environments. |
I can confirm that the preview (17.10) does not have this issue (at least for me). But its still magic .... VS connects to the MAC and it can build my application. No issues with the AOTCompiler but when i try to build commandline on the mac that i connect to (i want to do a dotnet publish so i have an .ipa file) i get the next issue to deal with. (https://stackoverflow.com/questions/78155352/build-of-maui-project-fails-after-update-of-dotnet-workload/) |
Here's the fun thing for me - I can connect and run all day from one computer, but not the other. Same VS version, same target Mac. One is over VPN - but I proxied past the web filter to ensure that wasn't the issue. However, I can confirm the @plppp2001 's workaround worked for me. Running 17.9.5 |
Had this problem in 17.9.4 and it went away after updating to 17.9.6. The mac has XCode 15.2 |
Updated to 17.9.6 and it worked (already had XCode 15.3 previously before it stopped working). |
Following setup is working fine here: Windows11 |
I currently have (working fine and I'm connected doing Release Builds without issue); Version 17.9.6 |
XCode V15.3 - Sonoma 14.4.1 on MacBook Pro (total reset this morning) Visual Studio 2022 Version 17.10.0 Preview 7.0 alongside Visual Studio 2022 Version 17.9.6 Two ongoing solutions: one Xamarin (with VS 17.9.6), one Maui (with VS 17.10.0) Xamarin solution pairs to mac. Can somebody help me? This is driving me crazy! |
Try restarting your modem/router? |
network is totally fine. thanks for answering though |
Now it's unavailable again。 |
You need to install the latest windows update also from 2 days ago.... |
It has nothing to do with this. The real problem is .NET SDK 8.0.300 The specific situation is: When I use the pair to mac function, it keeps appearing At first I thought this was a problem here on mac Finally, I compared the mac and windows environments and found the problem Mac:
Windows:
the ios workload`s version was 17.2.8053 instead of newest 17.2.8062! But in Then I found the folder name below After Copying the 17.2.8062 From The question is why [pair to mac] used the incorrect local dotnet instead of the dotnet installed via dotnet-install.sh? |
Description
When attempting to pair-to-mac I get the following error:
I have the following global.json:
I've tried using 8.0.101 and 8.0.102 as well with no luck. I'm using Visual Studio 17.9.0.
I've tried deleting
~/Library/Caches/Xamarin/XMA/SDKs/
on the Mac several times with no luck.The text was updated successfully, but these errors were encountered: