android-cli

The android-cli resource installs and configures Android CLI, Google's command-line tool for managing the Android development environment. It manages the CLI itself, SDK packages, and Android Virtual Devices (AVDs) in a single resource.

On macOS, Android CLI is installed via the official curl script (ARM64 and x86_64 supported). On Linux, only AMD64/x86_64 is supported.

Parameters

• sdkPath: (string) Path to the Android SDK directory. Written to ~/.androidrc as --sdk=<path>. Defaults to the android CLI's built-in default location if omitted.
• sdkPackages: (string[]) Android SDK packages to install declaratively. Package paths use forward-slash notation (e.g. platforms/android-35, build-tools/35.0.0, cmdline-tools/latest, platform-tools, system-images/android-35/google_apis_playstore/x86_64). Run android sdk list --all to see all available identifiers.
• emulators: (string[]) Android emulator profiles to create as AVDs. Each string is a hardware profile name (e.g. medium_phone, pixel_9). Emulators are always created after sdkPackages are installed. Run android emulator create --list-profiles to see available profiles.

Example usage

Install the CLI with essential SDK packages:

[
  {
    "type": "android-cli",
    "sdkPackages": [
      "cmdline-tools/latest",
      "platform-tools",
      "platforms/android-35",
      "build-tools/35.0.0"
    ]
  }
]

Full Android development environment with an emulator:

[
  {
    "type": "android-cli",
    "sdkPackages": [
      "cmdline-tools/latest",
      "platform-tools",
      "platforms/android-35",
      "build-tools/35.0.0",
      "system-images/android-35/google_apis_playstore/x86_64"
    ],
    "emulators": ["pixel_9"]
  }
]

Common emulator profiles

Notes

• Linux ARM64 is not supported. Only AMD64/x86_64 is supported on Linux.
• AVDs are removed using android emulator remove.
• Run android info to display the default SDK path in use.