The full message looks like this:

Could not find a driver for automationName 'UiAutomator2' and platformName 'Android'.
Have you installed a driver that supports those capabilities?
Run 'appium driver list --installed' to see.
(Lower-level error: Could not find installed driver to support given caps)

The usual advice is "install the driver". That fixes the first case. But many people get this error with the driver installed, and appium driver list --installed shows it. This article explains how Appium picks a driver, so you can tell which case you are in.

Short answer: read the Lower-level error at the end. "Could not find installed driver to support given caps" means the Appium server you started has no driver with that automationName in its Appium home. Most often the driver was installed into a different home: another user, another APPIUM_HOME, or a project-local Appium. A lower-level error that names a driver and lists its platformNames means the platformName does not match. Anything else, such as a missing module, means the driver is installed but cannot be loaded. Reinstall it.

How Appium picks a driver

Since Appium 2, installing Appium "only installs the core Appium server, without any drivers" (Appium's migration guide). Drivers are separate packages, installed into a directory called the Appium home.

When a new session request arrives, Appium (version 3.9.0 at the time of writing) does this:

  1. It requires platformName and appium:automationName in the capabilities. If either is missing, the request fails earlier with a different error.
  2. It goes through the drivers installed in its Appium home. Each driver declares one automationName and a list of platformNames in its package.json. For example, the UiAutomator2 driver declares UiAutomator2 and ["Android"].
  3. It compares both values without regard to case. uiautomator2 matches UiAutomator2, and android matches Android.
  4. It loads the matching driver's code. If any step fails, you get "Could not find a driver for automationName …", with the step's own error in brackets as the Lower-level error.

So there are three different failures behind one message. The lower-level error tells you which one.

Lower-level error 1: "Could not find installed driver to support given caps"

No installed driver declares this automationName. Either no such driver is installed in this server's Appium home, or the value is wrong.

Check the value first

The value must be the driver's declared automationName. Common ones: UiAutomator2 (UiAutomator2 driver), XCUITest (XCUITest driver), Espresso (Espresso driver). Case does not matter, but spelling does.

To see what your installed drivers declare, run:

appium driver list --installed --json

The JSON shows each installed driver with its automationName and platformNames.

Then check which Appium home the server uses

Appium keeps drivers in the directory named by APPIUM_HOME. If the variable is not set, the default is .appium in the current user's home directory. The extension list, appium driver install and the server all use the same rule. If you install the driver under one home and start the server under another, the server has no drivers.

The server log tells you which home it uses. Near the start, it prints a debug line like one of these:

The autodetected Appium home path: /Users/ci/.appium
The APPIUM_HOME environment variable: /opt/appium-home

Compare that path with where you installed the driver. These setups often split them:

  • Different users. The driver was installed by one user (or with sudo) and the server runs as another, for example as a CI agent or a system service. Each user has their own ~/.appium.
  • Different environments. APPIUM_HOME is set in your shell profile but not in the CI job, the IDE run configuration or the service that starts Appium. Or the other way round.
  • A fresh CI machine or container. The driver was installed on the image you built, but under a different user or home, or the step that installs it runs in a different job than the server.

The fix is the same each time: install the driver with the same user and the same APPIUM_HOME as the server, in the same environment.

# Run these in the same environment that starts the server.
echo "APPIUM_HOME=${APPIUM_HOME:-<not set: ~/.appium>}"
appium driver list --installed
appium driver install uiautomator2
appium

A project-local Appium uses the project's drivers

This case surprises many teams. If APPIUM_HOME is not set, Appium checks whether the current directory is inside an npm package that lists appium as a dependency. If it is, Appium "will load drivers and plugins defined in that package.json file instead" (Appium's guide to managing extensions).

So the same appium command can see different drivers depending on the directory you start it from. Inside a Node.js test project with appium in devDependencies, it uses the drivers listed in that package.json, not the ones in ~/.appium.

Pick one of the two ways and use it everywhere:

  • Add the drivers to the project like any other dependency, for example appium-uiautomator2-driver next to appium in devDependencies, and start the server with npx appium inside the project.
  • Or keep drivers in an Appium home: set APPIUM_HOME explicitly for both the install and the server. If it is set, the project check is skipped.

The guide recommends the npm way only "if you are already using npm for your project".

Lower-level error 2: "Driver '…' supports automationName '…', but Appium could not find support for platformName '…'"

The automationName matched, but the platformName is not in the driver's list. The message ends with the list, for example:

Supported platformNames are: ["Android"]

Check the spelling of platformName. The match ignores case but not other differences. Also check that the capability is not overwritten somewhere. Many test frameworks merge capabilities from several places (a base config, an environment file, a cloud provider's defaults), and the session gets the merged value.

platformName is a standard WebDriver capability, so it takes no appium: prefix. If you send appium:platformName, Appium logs a warning that it does not need the prefix and still uses it. But automationName is not standard. Without the prefix, Appium rejects the request with a different error: All non-standard capabilities should have a vendor prefix.

{
  "platformName": "Android",
  "appium:automationName": "UiAutomator2"
}

Lower-level error 3: the driver was found but could not be loaded

If the lower-level error is something else, for example Cannot find module …, Appium found a matching driver in its home but failed to load its code. The driver's files are incomplete or broken.

Reinstall it in the same Appium home:

appium driver uninstall uiautomator2
appium driver install uiautomator2

When you install a driver by its short name, Appium checks whether the version is compatible with the installed server. If the latest version is not, it looks for an older compatible one. A driver installed by other means, for example from a Git URL or a local path, skips that choice. After reinstalling, run the driver's own checks if it has any:

appium driver doctor uiautomator2

A related startup error: "Could not load the driver … because it is not installed"

If the server is started with --use-drivers, it loads only the listed drivers, and it fails at startup if one of them is not installed:

Could not load the driver 'xcuitest' because it is not installed.

The message also lists the drivers that are installed. This is the same home problem as above, found at startup instead of at session creation.

Checklist

  1. Read the Lower-level error at the end of the message.
  2. Check appium:automationName against appium driver list --installed --json.
  3. Find the Appium home in the server log and compare it with where the driver was installed.
  4. Install the driver with the same user and the same APPIUM_HOME as the server.
  5. Inside a Node.js project with appium as a dependency, either add the drivers to package.json or set APPIUM_HOME explicitly.
  6. For a platform mismatch, check platformName spelling and where the merged capabilities come from.
  7. For any other lower-level error, uninstall and reinstall the driver, then run appium driver doctor <driver>.

Sources

Checked on 2026-11-08 against the source and documentation of Appium 3.9.0 (current master of the appium repository) and the package.json manifests of the UiAutomator2, XCUITest and Espresso drivers: