maui: Pair to Mac failed with error "Workload manifest dependency 'Microsoft.NET.Workload.Emscripten' version '6.0.4' is lower..."

Description

Pair to Mac failed with error “Workload manifest dependency ‘Microsoft.NET.Workload.Emscripten’ version ‘6.0.4’ is lower than version ‘6.0.9’ required by manifest ‘microsoft.net.workload.mono.toolchain’”.

Steps to Reproduce

Install the latest build of Dev17.4 Preview 2 and use the script to install the MAUI(6.0.517) workload from main branch
On the Windows machine, create a new Blazor Hybrid project on the command line using the following: dotnet new maui-blazor -o iOSWindowsProject
Open the iOSWindowsProject solution with Visual Studio.
Select the “Pair to Mac” option in the Visual Studio toolbar.
Select the mac OS device that is connected to the network and press “Connect”.
In the next window, enter the username and password for the user account on the macOS machine.
Connect the machine.

ACTUAL: Pair to mac failed.

NOTE:

This issue does not repro when only installing Dev17.4 Preview 2, which includes MAUI version is 6.0.486.
This issue still repro after manually adding the following feeds in VS.

Version with bug

Unknown/Other (please specify)

Last version that worked well

Unknown/Other

Affected platforms

Windows

Affected platform versions

Windows SDK 6.0.400

Did you find any workaround?

Relevant log output

Workload manifest dependency 'Microsoft.NET.Workload.Emscripten' version '6.0.4' is lower than version '6.0.9' required by manifest 'microsoft.net.workload.mono.toolchain' [/Users/netcore/Library/Caches/Xamarin/XMA/SDKs/dotnet/sdk-manifests/6.0.400/microsoft.net.workload.mono.toolchain/WorkloadManifest.json]

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 1
Comments: 68 (6 by maintainers)

Most upvoted comments

I changed C:\Program Files\dotnet\sdk-manifests\6.0.300\microsoft.net.workload.mono.toolchain\WorkloadManifest file:

from:

{
  "version": "6.0.9",
  "depends-on": {
    "Microsoft.NET.Workload.Emscripten": "6.0.9"
  },............
...............

to:

{
  "version": "6.0.4",
  "depends-on": {
    "Microsoft.NET.Workload.Emscripten": "6.0.4"
  },............
.................

and it works and pair to mac correctly…

+14

hasanoruc on Sep 14, 2022

carlfranklin on Sep 13, 2022

@samhouts Are you able to request that the VS tooling team tests that .NET MAUI development is functional before shipping?

g4mb10r on Sep 19, 2022

kfrancis on Sep 28, 2022

Now fixed in VS 17.3.5 See: https://developercommunity.visualstudio.com/t/Failed-to-pair-to-Mac-with-error-Could-/10138259#T-N10159813

Forestbrook on Sep 28, 2022

Hi all,

I see alot of you manage to get it working by changing the version number in C:\Program Files\dotnet\sdk-manifests\6.0.300\microsoft.net.workload.mono.toolchain\WorkloadManifest.json

This does not work for me. It looks like VS copies WorkloadManifest.json directly from Nuget.

Does anybody know how to change that? Something to change in a NuGet.config?

Same here, none of the workarounds listed here seem to do anything. 6.0.9 just appears on the mac no matter what.

kfrancis on Sep 19, 2022

Hi, I managed to pair Mac with all simulators and build & run my MAUI IOS App in the IOS simulator. My workaround is below:

In folder C:\Program Files\dotnet\sdk-manifests, rename the 6.0.300 folder as 6.0.300_bak

Copy folder C:\Users<login user>.dotnet\sdk-advertising\6.0.300 to C:\Program Files\dotnet\sdk-manifests

Reboot my PC (not sure if it is neccessary but to play safe)

In my Mac, rename /library/Caches/Xamarin/XMA to XMA_bak

in PC, start VS2022 and pair with Mac. Build and run.

I found that the 6.0.300 in step 1 is newer than that in step 2. Hence, I reverted Microsoft.NET.Workload.Emscripten’ version 6.0.9 back to 6.0.4.

Hope it helps.

Thanks a ton, that worked. I can’t believe how many hours I’ve wasted on this issue. Unbelievable that the VS team would ship broken toolchains and dependencies without testing first. I hope we get a proper fix soon, fingers crossed.

inexuscore on Sep 18, 2022

I believe we just made the VS feedback public so you can track it now. The issue is resolved and pending release very soon! Thank you for your patience!!

samhouts on Sep 16, 2022

@EmilyFeng97 could you please link the VS Feedback ticket here when you get a chance?

I have file a new VS Feedback ticket 10138259 for this bug.

EmilyFeng97 on Sep 2, 2022