Can't build with preview - trouble conneting to mac server

RBrianLindahlRBrianLindahl R. Brian LindahlUSMember ✭✭
edited July 9 in Xamarin Live Player

I'm using VS 2017 preview 3, along with the xamarin updater. I was able to build fine a few hours ago. Now, even though the mac agent is connected successfully, i'm getting

The Xamarin Build Agent is not running on the Mac. An active Build Agent is required to perform the build

I've completely wiped xamarin from the mac and reinstalled vs-mac along with the alpha channel updates. i've also followed through all the steps in the 'connection troubleshooting' page. nothing jumps out at me from the logs, and a diagnostic build log doesn't show anything.

regular VS can build OK.

very frustrated. no clue what got changed. i had created a new xamarin app, and it built and ran in the live player just fine. then i went to xamarin university and was following along with the mytunes sample. downloaded it, tried to build, and couldn't.


  • BradChase.2654BradChase.2654 Brad Chase USMember ✭✭✭

    I am unfortunately getting the same thing now. I am trying every combination I can in terms of releases, VS2017, VS2017p4, VS2015 all channels... Cant seem to find one that works

  • bytebuilderbytebuilder Krlos C USMember ✭✭

    Same here. Has anyone found a solution for this?

  • bytebuilderbytebuilder Krlos C USMember ✭✭

    @RBrianLindahl @BradChase.2654 Just curious if yuou have you found a workaround for this issue. I am still running into it. :(

  • BradChase.2654BradChase.2654 Brad Chase USMember ✭✭✭
    edited July 19

    @bytebuilder Sure... you are not going to like the answer though... I formatted my machine. I am never installing Preview again thats for sure.

    Somehow the wires are crossing even though I thought they were not supposed to. My best advice would be to force it to forget all the macs by right clicking on them in the visual agent and forgetting. Move to stable channel on Mac and use VS 2017 (NON PREVIEW). Hope it works for ya :(.

    EDIT: After forgetting make sure to close and restart visual studio with a good delete of your bin/obj directories. Not that that will help much but its good practice when things start going haywire.

Sign In or Register to comment.