(in macOS) export PATH=”~/Library/Android/sdk/platform-tools”:$PATH.Pasting this command in terminal solves the issue in most cases: ** For Current Terminal Session: Note that setting ANDROID_HOME is required for some third party frameworks, so it does not hurt to add it. Save the profile file, then, re-start the terminal or run source ~/.bashrc (or whatever you just modified). Make sure to replace the path with the one where you installed platform-tools if it differs: export ANDROID_HOME='$HOME/Android/Sdk'Įxport PATH='$ANDROID_HOME/tools:$ANDROID_HOME/tools/bin:$ANDROID_HOME/platform-tools:$PATH'

Open the shell profile from step two, and at the bottom of the file, add the following lines. This might be (where $HOME is your user’s home directory) one of the following (or verify via Configure > SDK Manager in the Android Studio startup screen):įind out which shell profile to edit, depending on which file is used: This is how you do it:įind out where you installed the Android SDK. The dot is your current directory, and this tells Bash to use adb from there.īut actually, you should add platform-tools to your PATH, as well as some other tools that the Android SDK comes with. Therefore, if you are currently in the platform-tools directory, just call. You can check your current PATH with echo $PATH.īash will first try to look for a binary called adb in your Path, and not in the current directory. This is where the shell looks for executables.

Android studio adb not found mac