android studio adb shell not finding device

Kill off any adb instances on both the local and remote machines, since old ones will interfere, using one of these commands:Īlso make sure you are not running Android Studio on either machine, because it will automatically try to restart adb and Which -a to see what other adb binaries might be present.

You need to watch out here, because when ADB goes to launch the server, it might be using a different $PATH than the which command. Which adb /Users/wayne/android-sdk/platform-tools/adb If the output is not the same, you need to ensure you are running the version you downloaded earlier. You might have other versions that are in the $PATH as well,Ĭheck the versions on both machines, you should get the same output on both:Īdb -version Android Debug Bridge version 1.0.32 Once you have installed this, make sure it is the only version in your $PATH. Important otherwise you might get the error messageĪdb server version (32) doesn't match this client (34) killing. The first step is to make sure you have the same version of Android SDK Platform-tools installed on both machines. This works because adb is actually two processes, a client, and a server, and they use a local port 5037 to Laptop and using adb install, you can use an SSH tunnel and automatically forward the ports to make it look like the device isĬonnected locally. Instead of constantly copying the APK file manually to your However, thereĪre times when you are using a powerful remote build server via SSH. The ADB debugging tool is normally used to communicate with Android devices connected to your local machine.

Using ADB from a remote build machine with a local Android device over SSH Wayne Piekarski | Using ADB from a remote build machine with a local Android device over SSH wayne piekarski

Android studio adb shell not finding device