Forum Xamarin.iOS

Error Connecting to mac: Integrity check failed between deployed content and local copy.

I am attempting to connect to a new mac from VS 2017 on a win10 PC and its not working. I have enabled SSH/firewall is off on the mac. I can ping the mac and connect with SSH client just fine. Here is the output in my build window. The issue appears to a md5 mismatch between the XMA folder which is being copied to mac. Please help!

Starting connection to Mac 192.168.181.128...
Installing Broker 4.4.0.34...
Uploading Broker 4.4.0.34 (192/1887 KB) 10%...
Uploading Broker 4.4.0.34 (384/1887 KB) 20%...
Uploading Broker 4.4.0.34 (576/1887 KB) 30%...
Uploading Broker 4.4.0.34 (768/1887 KB) 40%...
Uploading Broker 4.4.0.34 (944/1887 KB) 50%...
Uploading Broker 4.4.0.34 (1136/1887 KB) 60%...
Uploading Broker 4.4.0.34 (1328/1887 KB) 70%...
Uploading Broker 4.4.0.34 (1520/1887 KB) 80%...
Uploading Broker 4.4.0.34 (1712/1887 KB) 90%...
Uploaded Broker 4.4.0.34 100%
Integrity check failed between deployed content and local copy. Server path: /Users/admin/Library/Caches/Xamarin/XMA/Broker/4.4.0.34, Local path: C:\Users\mark\AppData\Local\Temp\Xamarin\XMA\Broker\Broker.4.4.0.34.md5
Unable to install the Broker
Couldn't connect to 192.168.181.128. Please try again.
Disconnected from the Mac 192.168.181.128 (192.168.181.128)

Thanks!

Best Answer

  • MarkCollins.1768MarkCollins.1768 USMember
    Accepted Answer

    I have fixed this error by rename the C:\Users\mark\AppData\Local\Temp\Xamarin\XMA folder on my windows machine to XMAold. This apparently causes xamarin to recreate the folder/hashes when trying to connect to the mac again and it seemed to work.

Answers

  • MarkCollins.1768MarkCollins.1768 USMember
    Accepted Answer

    I have fixed this error by rename the C:\Users\mark\AppData\Local\Temp\Xamarin\XMA folder on my windows machine to XMAold. This apparently causes xamarin to recreate the folder/hashes when trying to connect to the mac again and it seemed to work.

  • ArchitektArchitekt USMember ✭✭

    Thanks so much. I just had this after my Mac updated to the latest OS and this fixed it.

Sign In or Register to comment.