Broker error #7882
Comments
|
I have reinstalled VS both on Windows and Mac and it still does not work. |
chamons
added
the
external-xamarin-vs
|
Looks like there is a problem with SCP in your Mac, possibly due to the SSH version. What's strange is that it comes with macOS and I haven't seen this error before with XMA. See the logs: I found a PR to fix this in the SSH.NET library: sshnet/SSH.NET#515 However, we should understand what is different on your Mac to cause this problem. |
|
@mauroa I tried updating SSH but that did not resolve it either. When I search the Internet I find old posts about broken user profiles. This is so annoying. Do I really have to reinstall all OS:es? As I wrote, there is no broker in the temp folder in macOS: To me it seems that the installer is broken. Here is my updated log: |
|
So I recreated my account on my Windows 10 VM and tried connecting: Now I get this: |
|
Hi, The reason why the Broker is not in the Mac is because we copy the Broker and Agents from Windows to the Mac (if not already copied) as part of the connection process. So, because SCP fails in your case, the copy couldn't be completed and then when we try to start the Broker process it fails complaining that the Broker is not there (which is correct). The focus here should be on trying to understand why SCP is not working on your Mac and what is causing it. The link I pointed to you about SSH.NET shows that this is a know problem. but they just fixed the way they handle that error on the client side. I'll continue investigating and let you know If I find something. |
|
What macOS version do you have? |
|
@mauroa macOS Catalina Beta 10.15.4 I recreated my users both in macOS and Windows 10 (Preview) in Parallels. when I try now, I get a message telling that my environment has not been properly configured. |
|
Observe that I run Stable VS 2019 now: Tried to run the It failed in PowerShell due to the syntax, and in Git Bash it executed did not do anything. So then I copied the key manually to There are no keys to copy from How can I troubleshoot this? |
|
I finally reinstalled macOS without losing my data and apps. Now I can connect again. I just think it is bad that you cannot fix the problem manually. |
|
@RobertSundstrom I have exactly the same problem. |
|
I have the same issue I do not want to try to reinstall Mac Os Here by I attach the Xamarin log files from windows |
|
i have the same error An error occurred while generating the SSH keys. Please check that the environment is properly configured. Details: cat: /Users/mohsen/Library/Caches/Xamarin/XMA/Keys/69277951-3d5f-44e0-abeb-e76fdee999b9: No such file or directory and also tried to delete cashes from windows and mac but didn't help |
what version of macOS did you just reinstalled ? |
|
I also ran into this issue after upgrading to macOS 10.15.4 today. |
|
There is a workaround you can do to connect: 1- copy the content of file C:\Users\xx\AppData\Local\Xamarin\MonoTouch\id_rsa.pub Restart Visual studio and Enjoy |
It worked, But now i am getting this error. "The Broker initialization exceeded the timeout of 60000 millisecs without receiving confirmation from the Broker process" |
|
Same here, after Mac update! |
|
Addressing the issue: For all who face the same issue The full temporary workaround finally is here [Until microsoft release the new update]: 1- Copy the content of file C:\Users\xx\AppData\Local\Xamarin\MonoTouch\id_rsa.pub 2- Paste it into mac ~/.ssh/authorized_keys in a New Line 3- Download the attached scp binary that I attached and replace it in your os x and decompress it
sudo mount -uw /B- Backup old SCP sudo cp /usr/bin/scp /usr/bin/scp.bakC- Replace SCP sudo cp ~/Downloads/scp /usr/bin/scpTry now connection and it should work now. |
|
Hello @eslamo , do you perhaps have any indication of when an update of Visual Studio for Windows might be available with the fix? I'm getting this error: |
I don't know the timeline of release actually but as I explained you can change the scp file temporarily and it should fix this error. |
|
Thanks, but access to /usr/bin is not allowed, same with "sudo mount -uw /" we have to wait for your release and meantime we can't do any work |
|
Thanks! Workaround fixes it. |
|
|
|
That's the correct answer man :) |
|
On a new OSX 10.15.4 VM Pasting the key gets a bit further, some pkg files get updated on OSX and then an error in VS 2019 states 'Error - An error occured while trying to start the Broker...'. Attempting to execute 'sudo mount -uw / generates the error message: 'mount_apfs: volume could not be mounted: Operation not permitted I was going to try to disable SIP to be able to replace scp by going into recover mode etc. - A bit horrible though. I can confirm that a Mac mini running 10.15.3 does not have the problem. |
I'm sure after disabling SIP everything will work as expected. |
Thanks! Oh, yes - it works - u-r-gold! |
|
This worked to get up and debugging on iOS again, but I can't build a release for distribution to the Apple Store because it's not syncing the Manual Provisioning settings (Signing Authority and Provisioning Profile). I've downloaded the manual profile for our team in Xcode 11.4, so I'm not sure why Xamarin isn't picking it up, and this is needed to Distribute the archive to the App Store. Any suggestions? |
|
@Magendanz I have same problem. I think actual version VS 2019 16.5.1 is totally bugged for iOS development... for example when I opened project in VS 2017 pair with Mac worked well before @eslamo things. Now in VS 2017 I have my provisioning profiles but in VS 2019 not... |
|
@Magendanz btw I tried now in VS 2019 on PC in "Tools -> Options -> Xamarin -> Apple accounts" sign in to my Apple ID and download manual my profiles there and it works. |
|
Thanks for the pointer, @pinkysek! I was unable to download the provisioning profiles because VS 2019 said that the certificate status was "Not In Keychain". In the past, it's just pulled these automatically from the Mac's Keychain Access app, but now I had to export the certificate as a .p12 from the Mac and then hit Import Certificate in VS 2019. After that was complete, I was back in business and successfully able to publish to the App Store. |
|
I re-imaged my MAC and also uninstalled and reinstalled VS 2019 on my PC and the error persists. An error occurred while generating the SSH keys. Please check that the environment is properly configured. Details: cat: /Users/robertwood/Library/Caches/Xamarin/XMA/Keys/e7ed6a6d-0283-4ce1-84fe-1c297229411b: No such file or directory I'm looking for an actual fix here... Not a workaround. |
|
This issue is marked as Closed. Other than the long-winded workaround, is the issue actually fixed? I'm not going to lie, after reading this thread I am not too keen on trying the workaround (I don't have the time) and this is critical functionality to some of us. |
|
For those who are using Mac OS inside virtual machine and have troubles starting the system in recovery mode. You can enable next boot in recovery mode by running following command in the terminal |
|
Visual Studio 16.5.2 which got published today fixed that issue for me. |
|
Hi Guys, With this latest version, it has broken the iOS ListView OnItemSelected - does anyone else have this issue? |
|
I am finding issues with navigation. My App uses Prism 7.2, XF 4.5 latest stable, Xcode 11.4 |
Are you experiencing the issue of command for OnItemSelected not getting fired ? Nothing happens when you select the item ? |
|
I got issues with Tap Gestures iOS (started after upgrading to 16.5.2 which did fix the connect to mac issue, Xamarin.iOS is at 13.16.0.11). |
the 16.5.2 fixed the deployment, but has broken the Tap Gesture in a ListView. I had an app which did work which was previously deployed in the simulator and that now does not work. So it seems when I synced by Windows machine with my mac, it pushed a Xamarin/Mono library which broke the simulator. |
did you try it after resetting and cleaning the simulator ? I did - but no success. I think the mono framework version could also be the culprit. Are you finding this issue on iPhone device as well or just on the simulator? |
Please this issue open until we get to validate the functionality fully after this fix is released. |
I am getting this on both Simulator and Device |
|
Please file new issues if you have a new and different problem than the one described here, otherwise it's unlikely we'll investigate it. |
I'm using WinSCP to make things easy. |
Helped me, too. Had to clear contents of directory "%LOCALAPPDATA%\Xamarin\MonoTouch" before. |
Did the update and still having trouble to install the Broker: Xamarin.Messaging.Integration.State.ServerStateContext|Information|0|Checking Xamarin iOS installation... |
|
Hello all
|
|
I too am back up and running. Thanks Xamarin Team for getting this issue resolved 😊
From: Marek Otulakowski <notifications@github.com>
Sent: April 1, 2020 11:23 AM
To: xamarin/xamarin-macios <xamarin-macios@noreply.github.com>
Cc: robertwood62 <robertwood62@hotmail.com>; Comment <comment@noreply.github.com>
Subject: Re: [xamarin/xamarin-macios] Broker error (#7882)
Hello all
The following scenario worked for me:
1. VS2019 update to 16.5.2
2. Mac connection from VS2017 completed successfully (install Mono etc.)
3. Connection to Mac from VS2019 completed correctly (install Broker etc.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fxamarin%2Fxamarin-macios%2Fissues%2F7882%23issuecomment-607314335&data=02%7C01%7C%7Ce4f127b224e546a20b3608d7d6508534%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637213513620603509&sdata=GGaakGZj8X3BXZgpEu9yUuJpku8bBuILd%2BbkbNjRwmk%3D&reserved=0>, or unsubscribe<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYKMNMM54XZ74ZVFPB7EMDRKNL4DANCNFSM4KUPVODQ&data=02%7C01%7C%7Ce4f127b224e546a20b3608d7d6508534%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637213513620613490&sdata=AA%2BFTflfSIUEgS9hjXU1nDAsaTXZovDeMFmOcVHHKCo%3D&reserved=0>.
|
Added new issue |
|
When you'll fix this issue? |
|
@Midnayt - As you can see this issue is currently closed. If you are seeing this with the latest Xamarin.iOS and Xcode please feel free to open a new issue filled out with details. |
ghost
locked as resolved and limited conversation to collaborators
and others
I don't know where to report this.
Install fails in VS on Windows due to there being no
/tmp/Broker-16.5.000.400-b7161529-ddc5-403c-a2f5-d9cfb785533f/Broker.zipI have tried to clean my installation (both Windows and macOS) but the problem remains.
Microsoft Visual Studio Community 2019 Preview
Version 16.5.0 Preview 2.0
Xamarin.iOS SDK 13.14.1.17
The text was updated successfully, but these errors were encountered: