- Getting Started with Test Suite
- Studio
- Test Suite - Studio
- Overview
- Testing activities and APIs
- Orchestrator
- Testing robots
- Test Manager
![](https://docs.uipath.com/_next/static/media/grid.05ebd128.png?w=3840&%3Bq=100)
Local Android devices
To set up a local device to work with the Mobile Automation activities, you need to run a local instance of Appium, and have the necessary tools to automate Android devices.
There are two types of local Android devices that you can automate:
- Physical - a physical Android device that you can connect to your local machine, through a USB cable.
- Emulator - an emulator for an Android device that's stored locally.
The list below describes the most used commands for setting up Appium in the context of Mobile Device Automation:
appium driver list
- lists installed drivers (recommended for Appium 2.0)adb devices
- lists the connected devicesadb start-server
- starts debugging serveradb kill-server
- stops the debugging serverctrl + c
- kills Appiumappium-doctor
- helps in debugging your Appium.
APK
or IPA
file to an URL that is anonymously accessible by the Appium server (e.g. Blob storage).
Installing applications from the Play Store or App Store is not possible, except if you manually automate these applications to install your specific application.
Follow the steps below to complete the prerequisites for configuring a local physical Android device:
JAVA_HOME
.
C:\Program Files\Java\jdk8
.
b. ANDROID_HOME variable. Points to the folder where Android SDK was installed.
ANDROID_HOME
Variable value: the path where the Android SDK is located on your machine. For example: C:\Users\Username\AppData\Local\Android\Sdk
Note: The Username
part, inside the Variable Value path, must be replaced with the actual name of the user operating on the machine.
-
Open the Node.js command prompt and install Appium:
- For Appium 1.0, run the following command:
npm install -g appium
. Appium 1.0 comes with all drivers installed. - For Appium 2.0, run the following command:
npm install -g appium@next
.
- For Appium 1.0, run the following command:
appium driver install
uiautomator2
.
For more information on Appium 1.0 configuration, see Quick Start Intro.
- Restart the computer to apply the changes.
-
Open the physical mobile device, and enable Developer Options.
- On your phone, navigate to Settings > Developer Options.
- Under the Networking section, open Default USB configuration and set it to Charging phone only.
- Enable USB debugging.
- On your phone, navigate to Settings > Developer Options.
- Under the Networking section, open Default USB configuration and set it to Charging phone only.
JAVA_HOME
.
C:\Program Files\Java\jdk8
.
b. ANDROID_HOME variable. Points to the folder where Android SDK was installed.
- Variable name:
ANDROID_HOME
-
Variable value: the path where the Android SDK is located on your machine. For example:
C:\Users\Username\AppData\Local\Android\Sdk
Note: TheUsername
part, inside the Variable Value path, must be replaced with the actual name of the user operating on the machine.- Open the Node.js command prompt and install Appium:
- For Appium 1.0, run the following command:
npm install -g appium
. Appium 1.0 comes with all drivers installed. - For Appium 2.0, run the following command:
npm install -g appium@next
.
appium driver install uiautomator2
.
For more information on Appium 2.0 configuration, see Quick Start Intro.
- Restart the computer to apply the changes.
Enable WebView debugging on the local device to allow Mobile Device Manager to recognize the majority of UI elements inside an application.
If Appium doesn't autodetect the Chrome or the WebView version on your Android, choose one of the options below:
- Setting up local Android devices
- Most used Appium commands
- Application Storage
- Configuring Local Physical Android Device
- Prerequisites
- Configuring Local Physical Android Device
- Configuring Local Emulated Android Device
- Prerequisites
- Creating Android Emulator
- Enabling Web and Hybrid Automation With WebDriver
- Adding Local Android Device in Mobile Device Manager