Fix INSTALL_FAILED error - adb server version doesn't match in Xamarin.Android

Fix INSTALL_FAILED adb server version doesn’t match Xamarin.Android

Today I would like to share with you how you can fix the following problem:

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.Debugging.targets: Warning: error: could not install *smartsocket* listener: Address already in use
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
List of devices attached
adb server version (32) doesn't match this client (36); killing...

1. Problem

You might be running two different ADB and the versions collide.

2. Solution

Verify the ADB version used by Xamarin:

About Xamarin > Show details > Android SDK: [PATH]

Make sure the PATH is the same as the one referenced in Genymotion.

Genymotion > Settings > ADB > Use custom Android SDK tools > Put PATH in Android SDK

This means that the adb used by Xamarin Studio to perform all deployment commands will be the same as the daemon used by the VM.

If you see the error adb server version (32) doesn't match this client (36) it’s probably because the PATHs are different.

Once you have set the same path, your app should deploy properly.


Always make sure that your ADB path is the same for Xamarin and the VM you deploy to. If you have any question, leave a comment here or hit me Twitter @Kimserey_Lam! See you next time!

Other posts you will like!


Popular posts from this blog

Manage assets and static files with Angular CLI

Prime NG data table for Angular

A complete SignalR with ASP Net Core example with WSS, Authentication, Nginx