adb devices")Ĭonsidering you have already downloaded SDK platform tools & trying to set adb path: If you go to the PATH by cd command, call adb functions with pre-fix ". If you change or update the PATH, simply call any adb functions, since you added the PATH as a global param. Go to the path we found above by " cd ~/Library/Android/sdk/platform-tools" Note, this command won't print any result, if you want to make sure you changed PATH successfully, call " export | grep PATH" to see what the PATH is.Īdd more definition for the PATH global param (which I recommend) by: " export PATH=~/Library/Android/sdk/platform-tools:$PATH" or " export PATH=$PATH:~/Library/Android/sdk/platform-tools" There are 3 ways mentioned by many people:Ĭhange the PATH global param (which I won't recommend) by: " export PATH=~/Library/Android/sdk/platform-tools" which is the directory you got from above. Try the one without this code, you will understand what I mean.Ģ) Go to where we installed adb. " 2> /dev/null" -> ignore find results denied by permission.
Please note there is a space before the "/" character -> only find in User directory not all the computer.Try this in your terminal/ command line, " find / -name "platform-tools" 2> /dev/null" (Note: I didn't test in Window yet, but it works with Mac for sure). However, in case you could NOT remember this such long directory, you can quickly find it by the command " find". Window, it could be in: " %USERPROFILE%\AppData\Local\Android\sdk\platform-tools\". Mac, it could be in: " ~/Library/Android/sdk/platform-tools" + The reason is: you are in the wrong directory (means it doesn't contain adb executor).ġ) Find where the adb was installed.
0 kommentar(er)
