cannot build IOS after updating VS. MSBuild was unable to connect to the Mac. it IS connected to Mac?

[exquirentibus]

Apple platform

macOS, iOS

Framework version

net9.0-*

Affected platform version

VS 2022 to 17.14.8 preview 1.0 .NET SDK: Version: 9.0.302

Description

I was able to build .NET9 Maui for IOS 2 days ago. I upgraded VS 2022 to 17.14.8 preview 1.0 which updated .NET to
.NET SDK: Version: 9.0.302
Host: Version: 9.0.7

Now, I connect to Address='172.16.0.113' using Tools->IOS->Pair to Mac and have it show connected. I select the tethered iPhone from IOS Remove devices.

And now when I clean and build in release mode, I get:

C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk.net9.0_18.5\18.5.9207\tools\msbuild\iOS\Xamarin.Messaging.Build.targets(114,3): error : MSBuild was unable to connect to the Mac with Address='172.16.0.113' and User='xxxx'. This connection is separate from Visual Studio and without it the project can't build. Please try building again or report this problem if the issue persists

Steps to Reproduce

I've restarted both the MacStudio with Sequoia 15.5 and running latest Xcode 16.4 and my Windows 10 box. No change.

Did you find any workaround?

No

Build logs

even some of the log files have my full name so I must pass

[exquirentibus]

I also tried to build on VS 17.12.1 which also fails with the same exact error msg, so Visual Studio does Not seem to be the problem?

I tried putting global.json
{
"sdk": {
"version": "9.0.205"
}
}
in the folder with my solution and dotnet --info confirms that VS is now using that version.

I rebooted the Mac, restarted VS.

However, VS 2022 17.14.8 preview 1.0 fails in exactly the same way?

I also tried VS 17.12.1, but Again ...

MSBuild was unable to connect to the Mac with Address='172.16.0.113' and User='xxx'. This connection is separate from Visual Studio and without it the project can't build. Please try building again or report this problem if the issue persists

Going back to an earlier versions shouldn't be rocket science? Are there other steps?

[exquirentibus]

I can ssh into the mac without issue from Windows. ssh xxxx@172.16.0.113 (it created a new fingerprint) and asked me for my password. Then I could see the mac in the dos prompt.

So I can pair and watch the progress as the .NET libraries etc. are all setup on the mac.

I can see my tethered iPhone in VS.

I can directly ssh into the Mac.

I can do .. Everything .. except .. BUILD? And it worked fine before the VS upgrade which upgraded .NET9 also.

going back to the previous .NET with global.json doesn't get the build to work. Build still complains about the connection?

This is Not making any sense? How do I resolve this??

[rolfbjarne]

Please get an MSBuild binlog, this will contain a more detailed description of the failure.

[Felix-Dev]

We are seeing the same issue after updating VS from 17.13.4 to 17.14.8. Building via the command line works when I manually move the Mac .NET SDK bits from /Users/{username}/Library/Caches/Xamarin/XMA/SDK to /Users/{username}/Library/Caches/maui/PairToMac/SDKs.

[AurelienMGA38]

I've had the same error since upgrading VS to 17.14.8.
Opposite, I have a MAcBook Air in Sequoia 15.5 with XCode 16.4.

Error with Diagnostic.txt

[exquirentibus]

Please get an MSBuild binlog, this will contain a more detailed description of the failure.

after creating a new 'dev' user on my mac, going thu all the motions to create those logs (a Lot of steps to create new Mac account and get that setup with Xcode), I carefully read what the logs include. Can't do it as my project files, etc. include sensitive information.

I have generic setup. Mac Studio with latest Sequoia 15.5 Windows 10-64 fully patched. If you tell me specifically what you want from the logs, I can open them with the log viewer and give you that portion?

It failed exactly the same way when trying to build with that new dev account. I can see my tethered iPhone from Windows VS 2022?

As I can pair, and also ssh, this is something .NET9 changed 2 days ago .. that affects Everyone, all versions of VS (I tried a much earlier untouched VS to test), and even when using a global.json to go Back to a previous .NET.

I only upgraded hoping that it would fix Sentry, which the Last .NET update killed for IOS.

So I'm stuck between a rock and a hard place and a bit frustrated as I have a bug in my IOS app that I .. Need .. to fix.

There really needs to be a simpler way to get useful logging info that does Not contain .. Everything .. as this is a public forum?

There should also be a way to roll back to a previous version (or possibly I'm unaware of the proper way)?

I can move back to .. Any .. Xcode version with ease? Why can't I do that with VS and .NET?

Sorry to sound irritated but .. no doubt as you also are .. I'm stressed and behind on my work.

[MPoels]

I have the same problem, very frustrating, same issue need to fix the app, but can not build it!!
Wish I did not update VS2022 to 17.14.8 each time with an update I ran into issues with maui development. It takes more development time to produce a working environment again than the actual code changes take in the App.

My error:
C:\Program Files\dotnet\packs\Microsoft.iOS.Windows.Sdk.net9.0_18.5\18.5.9207\tools\msbuild\iOS\Xamarin.Messaging.Build.targets(114,3): error : MSBuild was unable to connect to the Mac with Address='xx.xx.xx.xx' and User='xxxxxx'. This connection is separate from Visual Studio and without it the project can't build. Please try building again or report this problem if the issue persists

I have no clue how to fix that, as the link with the apple machine, (after doing a lot of package updates) is established. And also reconnects well. Updating the packetstuff on the Apple machine has probably created the problem. But what a mess!

Frustrated user!

[exquirentibus]

@rolfbjarne

from the logs I created, maybe this is of use? it created 6 nearly identical MSBuild_CommTrace_PID_20040.txt files. I'm including from a few files here:

`OutOfProc Endpoint Packet Pump (TID 4) 638877591506608271 + 3.9054ms: Waiting for connection 900000 ms...
OutOfProc Endpoint Packet Pump (TID 4) 638877591506608271 + 0ms: Parent started connecting. Reading handshake from parent
OutOfProc Endpoint Packet Pump (TID 4) 638877591506608271 + 0ms: Building handshake for node type X64, NodeReuse, (version 1): options 16777228.
OutOfProc Endpoint Packet Pump (TID 4) 638877591506608271 + 0ms: Handshake salt is
OutOfProc Endpoint Packet Pump (TID 4) 638877591506608271 + 0ms: Tools directory root is C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin
OutOfProc Endpoint Packet Pump (TID 4) 638877591506686414 + 7.8143ms: Successfully connected to parent.
OutOfProc Endpoint Packet Pump (TID 4) 638877591506725454 + 3.904ms: Changing link status from Inactive to Active
OutOfProc Endpoint Packet Pump (TID 4) 638877591506725454 + 0ms: Entering read loop.
(TID 1) 638877591567158175 + 6043.272ms: Shutting down with reason: BuildCompleteReuse, and exception: .
OutOfProc Endpoint Packet Pump (TID 4) 638877591567353449 + 19.5274ms: Disconnecting voluntarily
OutOfProc Endpoint Packet Pump (TID 4) 638877591567353449 + 0ms: Changing link status from Active to Failed
OutOfProc Endpoint Packet Pump (TID 4) 638877591567353449 + 0ms: Ending read loop
(TID 1) 638877591567353449 + 0ms: Changing link status from Failed to Inactive
(TID 1) 638877591567978482 + 62.5033ms: Shut down complete.

(TID 1) 638877595000084543 + 0ms: Shutting down with reason: ConnectionFailed, and exception: .
(TID 1) 638877595000084543 + 0ms: Changing link status from Failed to Inactive
(TID 1) 638877595000240776 + 15.6233ms: Shut down complete.

(TID 1) 638877595000006396 + 3.9058ms: Attempting connect to PID 14264 with pipe MSBuild14264 with timeout 30 ms
(TID 1) 638877595000006396 + 0ms: Writing handshake part 0 (16777228) to pipe MSBuild14264
(TID 1) 638877595000006396 + 0ms: Writing handshake part 1 (1405299679) to pipe MSBuild14264
(TID 1) 638877595000045449 + 3.9053ms: Writing handshake part 2 (17) to pipe MSBuild14264
(TID 1) 638877595000045449 + 0ms: Writing handshake part 3 (14) to pipe MSBuild14264
(TID 1) 638877595000045449 + 0ms: Writing handshake part 4 (14) to pipe MSBuild14264
(TID 1) 638877595000045449 + 0ms: Writing handshake part 5 (31908) to pipe MSBuild14264
(TID 1) 638877595000045449 + 0ms: Writing handshake part 6 (1) to pipe MSBuild14264
(TID 1) 638877595000045449 + 0ms: Reading handshake from pipe MSBuild14264
(TID 1) 638877595000084543 + 3.9094ms: Successfully connected to pipe MSBuild14264...!
(TID 1) 638877595000084543 + 0ms: Shutting down node with pid = 14264
(TID 1) 638877595000084543 + 0ms: MSBUILDNODEHANDSHAKESALT="", msbuildDirectory="C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin", enableNodeReuse=True, enableLowPriority=False
(TID 1) 638877595000084543 + 0ms: Building handshake for node type X64, NodeReuse, (version 1): options 16777228.
(TID 1) 638877595000084543 + 0ms: Handshake salt is
(TID 1) 638877595000084543 + 0ms: Tools directory root is C:\Program Files\Microsoft Visual Studio\2022\Preview\MSBuild\Current\Bin
(TID 1) 638877595000123569 + 3.9026ms: Attempting connect to PID 20040 with pipe MSBuild20040 with timeout 30 ms
(TID 1) 638877595000123569 + 0ms: Writing handshake part 0 (16777228) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 1 (1405299679) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 2 (17) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 3 (14) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 4 (14) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 5 (31908) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Writing handshake part 6 (1) to pipe MSBuild20040
(TID 1) 638877595000123569 + 0ms: Reading handshake from pipe MSBuild20040
(TID 1) 638877595000162632 + 3.9063ms: Successfully connected to pipe MSBuild20040...!
(TID 1) 638877595000162632 + 0ms: Shutting down node with pid = 20040
`

[TonyLugg]

Me too. I can pair to the Mac but builds end in the error. Mac OS 15.5. VS 17.14.8