对于那些在Windows 10/x64上为Appium安装Android命令行工具的人，请执行以下操作:

Download latest Command line tools from android i.e. commandlinetools-win-6200805_latest.zip Unzip the downloaded file Create directory for storing commandline tools somewhere on your disk, with following path included: android/cmdline-tools/latest Basically when You unzip this Cmd line tools, just rename tools directory to latest and make sure You put this latest folder in android/cmdline-tools directory somewhere on your disk Create ANDROID_HOME environment variable for directory that stores the cmdline tools directory location like: C:\YourLocationWhereYouStoreTheDirectory\android\cmdline-tools\latest Create new entry in Path environment variable as %ANDROID_HOME%\bin

Android SDK工具现在休息在以下位置:“android_sdk/cmdline-tools/version/bin/”;

因此，在Windows操作系统中解决此问题(其他操作系统也一样)，请执行以下操作:

在android_sdk文件夹中，创建文件夹:cmdline-tools，并在其中创建另一个文件夹:version extract / put all your files "/bin /lib注意和源代码。此版本文件夹中的“属性”文件。 将ANDROID_HOME设置为android_sdk文件夹。 添加到系统路径:android_sdk\cmdlineAndroidSDK\cmdline-tools\version\bin\

类似地，将Android SDK平台工具放在android_sdk/ Platform - Tools /中，并在系统变量下的环境变量中添加相应的PATH

我在新Mac上下载独立命令行工具(commandlinetools-mac-6200805_latest)时就遇到了这种情况。

基于这里所有的答案，我能够让它像这样工作

# Define ANDROID_HOME, if not defined already
export ANDROID_HOME="~/Library/Android/sdk"

# Create the folder if missing
mkdir -p $ANDROID_HOME

# Let the tool know that it should use that SDK location. 
sdkmanager --list --sdk_root=$ANDROID_HOME

——sdk_root选项的文档说“使用指定的SDK根而不是包含此工具的SDK”。这让我想到，尽管该工具是独立发布的，但它有望成为SDK安装包的一部分。

这里总结了几篇有用的文章，对于想要快速片段的人，例如插入Dockerfile，下面的脚本对我来说很有用:

RUN mkdir -p /opt/android/cmdline-tools/latest \
    && cd /opt/android/cmdline-tools/latest \
    && wget https://dl.google.com/android/repository/commandlinetools-linux-6858069_latest.zip \
    && bsdtar --strip-components=1 -xvf commandlinetools-linux-6858069_latest.zip \
    && yes | bin/sdkmanager --licenses \
    && bin/sdkmanager "build-tools;29.0.2" "platforms;android-29" \
    && rm commandlinetools-linux-6858069_latest.zip

It just requires bsdtar to be installed (it's usually packaged in popular distributions). Android platform/build tools version 29 are installed, and Android sdk root will be then located in /opt/android. While this setup works for me without warnings as it is, I have an issue when reinstalling packages already installed, or possibly installing different version of the packages: it clashes with packages already present and create bogus directories in the sdk root, with -2, -3 suffixes. These directories are then ignored, and warnings like Observed package id 'emulator' in inconsistent location are printed, so this behavior is definitely not desirable. If you have a fix for that please write it in the comments or, if you are confident enough, just edit the script with the exact fix.

由于有新的更新，文档中没有提到一些更改。在解压缩命令行工具包之后，您将得到的最上面的目录是cmdline-tools。将解压缩目录从cmdline-tools重命名为tools，并将其放在$C:/Android/cmdline-tools下

现在它看起来像$C:/Android/cmdline-tools/tools

它会完美地工作。

简单的解决方案:

打开Android Studio工具菜单， SDK管理器在窗口中出现 上面是内嵌板， 选择SDK工具面板勾选Android SDK命令行工具 选择窗口底部附近的Apply按钮