Xamarin.forms: [Bug] Cannot pair and build project from MacOS to Visual Studio WIndows after upgrade MacOS

Created on 24 Mar 2020 · 9Comments · Source: xamarin/Xamarin.Forms

After upgrade MacOS Catalina from version 10.15.3 to 10.15.4 on Macbook Pro 2018, I cannot pair my PC (Windows 1909) to previously mentioned Macbook. Issue can be also related to the newest version of XCode but I am not sure. After that I tried to update Xamarin from Visual Studio on my PC to latest version and I also tried doing it on my Mac.

Error: Xamarin.Messaging.Integration.State.ServerStateContext|Error|0|An error occurred while trying to start the Broker...

unverified bug

Source

KSYMEK

👍3

Most helpful comment

Hi everyone.
From macOS 10.15.4, there was an update on OpenSSH which is breaking our SSH layer, so we crash when trying to copy the Mac Agent files over SCP to the Mac. That causes the connection to never complete.
We've already fixed it and the fix will be available on the next VS 16.6 P2 and also on the next 16.5 Service Release.
I'm closing this issue since it's fixed and pending to be released.
Thanks.

mauroa on 26 Mar 2020

🎉3

All 9 comments

After updating to the newest XCode, did you open XCode? Sometimes you have to run it once so it can install additional components.

hartez on 25 Mar 2020

Yes I tried it, I forgot to mention it.

KSYMEK on 25 Mar 2020

Same issue here : /

MacOS Catalina - 10.15.4
Visual Studio Enterprise 2019 - 16.5.1

SpongeDude on 25 Mar 2020

Have you tried upgrading VS for Windows to 16.5.1 ?

I notice a pair to mac issue resolved in the latest VS.
https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes#16.5.1

The actual bug they fixed :
https://developercommunity.visualstudio.com/content/problem/919385/cant-pair-with-macos.html

haavamoa on 25 Mar 2020

Same issue after upgrading to MacOS Catalina - 10.15.4 and Xcode 11.4.

Opened Xcode and when prompted, installed the necessary components.

VS Professional 16.5.1 is unable to pair.

adamswallows on 25 Mar 2020

👎1

Maybe leaving a comment in that last link can help you out? I mean they claim to have solved it.

haavamoa on 25 Mar 2020

mauroa on 26 Mar 2020

🎉3

Is there a schedule as to when VS 16.5 with this fix will be released?

solomonfried on 30 Mar 2020

@mauroa this sounds promising, thanks. Do you already know in which VS release the fix will be available? I can't find it on the release notes of 16.6 P2 nor is there any 16.5 service release announced. I'm on VS 16.5.1 and would do everything to get the dev team rolling again...