Appium

getLogTypes

Get available log types.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getLogTypes()

Returns

• <String[]> logTypes: The list of available log types, example: browser, driver.

---

getLogs

Get the log for a given log type. Log buffer is reset after each request.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getLogs(type)

Parameters

Name	Type	Details
type	string	the log type

Returns

• <Object[]> logs: The list of log entries.

---

getSession

Retrieve the capabilities of the current session.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use getAppiumSessionCapabilities instead

Usage

driver.getSession()

Returns

• <Object> capabilities: An object describing the session's capabilities.

---

getAppiumContext

Appium command. More details can be found in the official protocol docs.

Usage

driver.getAppiumContext()

Returns

• <Context> context: a string representing the current context or null representing 'no context'

---

switchAppiumContext

Appium command. More details can be found in the official protocol docs.

Usage

driver.switchAppiumContext(name)

Parameters

Name	Type	Details
name	string	a string representing an available context

---

getAppiumContexts

Appium command. More details can be found in the official protocol docs.

Usage

driver.getAppiumContexts()

Returns

• <Context[]> contexts: an array of strings representing available contexts, e.g. 'WEBVIEW', or 'NATIVE'

---

getAppiumCommands

Retrieve the endpoints and BiDi commands supported in the current session.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getAppiumCommands()

Returns

• <Object> commands: Supported endpoints and BiDi commands, each grouped into common, driver-specific, and plugin-specific endpoints/commands.

---

getAppiumExtensions

Retrieve the extension commands supported in the current session.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getAppiumExtensions()

Returns

• <Object> commands: Supported extension commands, grouped into driver-specific and plugin-specific commands.

---

getAppiumSessionCapabilities

Retrieve the capabilities of the current session.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getAppiumSessionCapabilities()

Returns

• <Object> capabilities: An object describing the session's capabilities.

---

appiumShake

Perform a shake action on the device. This is the raw Appium protocol endpoint. Prefer the shake mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the shake mobile command (driver.shake()) instead

Usage

driver.appiumShake()

Support

---

appiumLock

Lock the device. This is the raw Appium protocol endpoint. Prefer the lock mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the lock mobile command (driver.lock()) instead

Usage

driver.appiumLock(seconds)

Parameters

Name	Type	Details
seconds optional	number	how long to lock the screen (iOS only)

Support

---

appiumUnlock

Unlock the device. This is the raw Appium protocol endpoint. Prefer the unlock mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the unlock mobile command (driver.unlock()) instead

Usage

driver.appiumUnlock()

Support

---

appiumIsLocked

Check whether the device is locked or not. This is the raw Appium protocol endpoint. Prefer the isLocked mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the isLocked mobile command (driver.isLocked()) instead

Usage

driver.appiumIsLocked()

Returns

• <boolean> isLocked: True if the device is locked, false if not

Support

---

startRecordingScreen

Start recording the screen.

Appium command. More details can be found in the official protocol docs.

Usage

driver.startRecordingScreen(options)

Parameters

Name	Type	Details
options optional	object	command parameters that can contain keys like: remotePath, username, password, method, forceRestart, timeLimit, videoType, videoQuality, videoFps, bitRate, videoSize, bugReport (see more description in Appium docs)

Support

---

stopRecordingScreen

Stop recording screen.

Appium command. More details can be found in the official protocol docs.

Usage

driver.stopRecordingScreen(remotePath, username, password, method)

Parameters

Name	Type	Details
remotePath optional	string	The path to the remote location, where the resulting video should be uploaded. The following protocols are supported http/https, ftp. This option only has an effect if there is screen recording process in progreess and forceRestart parameter is not set to true. Null or empty string value (the default setting) means the content of resulting file should be encoded as Base64.
username optional	string	The name of the user for the remote authentication.
password optional	string	The password for the remote authentication.
method optional	string	The http multipart upload method name. The 'PUT' one is used by default.

Returns

• <string> response: Base64 encoded string. If remote_path is set, the response is empty string

Support

---

appiumGetPerformanceDataTypes

Returns the information types of the system state which is supported to read as like cpu, memory, network traffic, and battery. This is the raw Appium protocol endpoint. Prefer the getPerformanceDataTypes mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getPerformanceDataTypes mobile command (driver.getPerformanceDataTypes()) instead

Usage

driver.appiumGetPerformanceDataTypes()

Returns

• <string[]> performanceTypes: The available performance data types (cpuinfo|batteryinfo|networkinfo|memoryinfo)

Support

---

appiumGetPerformanceData

Returns the information of the system state which is supported to read as like cpu, memory, network traffic, and battery. This is the raw Appium protocol endpoint. Prefer the getPerformanceData mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getPerformanceData mobile command (driver.getPerformanceData()) instead

Usage

driver.appiumGetPerformanceData(packageName, dataType, dataReadTimeout)

Parameters

Name	Type	Details
packageName	string	the package name of the application
dataType	string	the type of system state which wants to read. It should be one of the supported performance data types
dataReadTimeout optional	number	the number of attempts to read

Returns

• <string[]> performanceData: The information type of the system state which is supported to read as like cpu, memory, network traffic, and battery

Support

---

appiumPressKeyCode

Press a particular key on the device. This is the raw Appium protocol endpoint. Prefer the pressKeyCode mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the pressKeyCode mobile command (driver.pressKeyCode()) instead

Usage

driver.appiumPressKeyCode(keycode, metastate, flags)

Parameters

Name	Type	Details
keycode	number	keycode to press
metastate optional	number	meta state to press the keycode with
flags optional	number	flags for the keypress

Support

---

appiumLongPressKeyCode

Press and hold a particular key code on the device. This is the raw Appium protocol endpoint. Prefer the longPressKeyCode mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the longPressKeyCode mobile command (driver.longPressKeyCode()) instead

Usage

driver.appiumLongPressKeyCode(keycode, metastate, flags)

Parameters

Name	Type	Details
keycode	number	keycode to press on the device
metastate optional	number	metastate for the keypress
flags optional	number	flags for the keypress

Support

---

appiumSendKeyEvent

Send a key code to the device. This is the raw Appium protocol endpoint. Prefer the pressKeyCode mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the pressKeyCode mobile command (driver.pressKeyCode()) instead

Usage

driver.appiumSendKeyEvent(keycode, metastate)

Parameters

Name	Type	Details
keycode	string	keycode to press
metastate optional	string	meta state to press the keycode with

Support

---

rotateDevice

Rotate the device in three dimensions.

Appium command. More details can be found in the official protocol docs.

Usage

driver.rotateDevice(x, y, z)

Parameters

Name	Type	Details
x	number	x offset to use for the center of the rotate gesture
y	number	y offset to use for the center of the rotate gesture
z	number	z offset to use for the center of the rotate gesture

Support

---

appiumGetCurrentActivity

Get the name of the current Android activity. This is the raw Appium protocol endpoint. Prefer the getCurrentActivity mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getCurrentActivity mobile command (driver.getCurrentActivity()) instead

Usage

driver.appiumGetCurrentActivity()

Returns

• <string> activity: Name of the current activity

Support

---

appiumGetCurrentPackage

Get the name of the current Android package. This is the raw Appium protocol endpoint. Prefer the getCurrentPackage mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getCurrentPackage mobile command (driver.getCurrentPackage()) instead

Usage

driver.appiumGetCurrentPackage()

Returns

• <string> package: Name of the current package

Support

---

installApp

Install the given app onto the device.

Appium command. More details can be found in the official protocol docs.

Usage

driver.installApp(appPath, options)

Parameters

Name	Type	Details
appPath	string	Path to application .apk file
options optional	object	Driver-specific installation options

Support

---

activateApp

Activate the given app on the device

Appium command. More details can be found in the official protocol docs.

Usage

driver.activateApp(appId, bundleId, options)

Parameters

Name	Type	Details
appId optional	string	App package ID (required for Android)
bundleId optional	string	Bundle ID (required for iOS)
options optional	object	Driver-specific launch options

Support

---

removeApp

Remove an app from the device.

Appium command. More details can be found in the official protocol docs.

Usage

driver.removeApp(appId, bundleId, options)

Parameters

Name	Type	Details
appId optional	string	App package ID (required for Android)
bundleId optional	string	Bundle ID (required for iOS)
options optional	object	Driver-specific uninstall options

Returns

• <boolean> didRemovalSucceed: Return true if uninstall was successful, false if not

Support

---

terminateApp

Terminate the given app on the device

Appium command. More details can be found in the official protocol docs.

Usage

driver.terminateApp(appId, bundleId, options)

Parameters

Name	Type	Details
appId optional	string	App package ID (required for Android)
bundleId optional	string	Bundle ID (required for iOS)
options optional	object	Driver-specific termination options

Support

---

isAppInstalled

Check whether the specified app is installed on the device.

Appium command. More details can be found in the official protocol docs.

Usage

driver.isAppInstalled(appId, bundleId)

Parameters

Name	Type	Details
appId optional	string	App package ID (required for Android)
bundleId optional	string	Bundle ID (required for iOS)

Returns

• <boolean> isAppInstalled: Return true if installed, false if not

Support

---

queryAppState

Get the given app status on the device

Appium command. More details can be found in the official protocol docs.

Usage

driver.queryAppState(appId, bundleId)

Parameters

Name	Type	Details
appId optional	string	App package ID (required for Android)
bundleId optional	string	Bundle ID (required for iOS)

Returns

• <number> appStatus: 0 is not installed. 1 is not running. 2 is running in background suspended. 3 is running in background. 4 is running in foreground

Support

---

hideKeyboard

Hide soft keyboard.

Appium command. More details can be found in the official protocol docs.

Usage

driver.hideKeyboard(strategy, key, keyCode, keyName)

Parameters

Name	Type	Details
strategy optional	string	hide keyboard strategy (UIAutomation only), available strategies - 'press', 'pressKey', 'swipeDown', 'tapOut', 'tapOutside', 'default'
key optional	string	key value if strategy is 'pressKey'
keyCode optional	string	key code if strategy is 'pressKey'
keyName optional	string	key name if strategy is 'pressKey'

Support

---

isKeyboardShown

Whether or not the soft keyboard is shown.

Appium command. More details can be found in the official protocol docs.

Usage

driver.isKeyboardShown()

Returns

• <boolean> isKeyboardShown: True if the keyboard is shown

Support

---

pushFile

Place a file onto the device in a particular place.

Appium command. More details can be found in the official protocol docs.

Usage

driver.pushFile(path, data)

Parameters

Name	Type	Details
path	string	path to install the data to
data	string	contents of file in base64

Support

---

pullFile

Retrieve a file from the device's file system.

Appium command. More details can be found in the official protocol docs.

Usage

driver.pullFile(path)

Parameters

Name	Type	Details
path	string	path on the device to pull file from

Returns

• <string> response: Contents of file in base64

Support

---

pullFolder

Retrieve a folder from the device's file system.

Appium command. More details can be found in the official protocol docs.

Usage

driver.pullFolder(path)

Parameters

Name	Type	Details
path	string	path to an entire folder on the device

Returns

• <string> response: Zip file of the folder contents in base64

Support

---

appiumToggleAirplaneMode

Toggle airplane mode on device. This is the raw Appium protocol endpoint. Prefer the toggleAirplaneMode mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleAirplaneMode mobile command (driver.toggleAirplaneMode()) instead

Usage

driver.appiumToggleAirplaneMode()

Support

---

appiumToggleData

Switch the state of data service. This is the raw Appium protocol endpoint. Prefer the toggleData mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleData mobile command (driver.toggleData()) instead

Usage

driver.appiumToggleData()

Support

---

appiumToggleWiFi

Switch the state of the wifi service. This is the raw Appium protocol endpoint. Prefer the toggleWiFi mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleWiFi mobile command (driver.toggleWiFi()) instead

Usage

driver.appiumToggleWiFi()

Support

---

appiumToggleLocationServices

Switch the state of the location service. This is the raw Appium protocol endpoint. Prefer the toggleLocationServices mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleLocationServices mobile command (driver.toggleLocationServices()) instead

Usage

driver.appiumToggleLocationServices()

Support

---

appiumToggleNetworkSpeed

Set network speed (Emulator only). This is the raw Appium protocol endpoint. Prefer the toggleNetworkSpeed mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleNetworkSpeed mobile command (driver.toggleNetworkSpeed()) instead

Usage

driver.appiumToggleNetworkSpeed(netspeed)

Parameters

Name	Type	Details
netspeed	string	Network type - 'full','gsm', 'edge', 'hscsd', 'gprs', 'umts', 'hsdpa', 'lte', 'evdo'

Support

---

appiumOpenNotifications

Open Android notifications. This is the raw Appium protocol endpoint. Prefer the openNotifications mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the openNotifications mobile command (driver.openNotifications()) instead

Usage

driver.appiumOpenNotifications()

Support

---

appiumStartActivity

Start an Android activity by providing package name and activity name. This is the raw Appium protocol endpoint. Prefer the startActivity mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the startActivity mobile command (driver.startActivity()) instead

Usage

driver.appiumStartActivity(appPackage, appActivity, appWaitPackage, appWaitActivity, intentAction, intentCategory, intentFlags, optionalIntentArguments, dontStopAppOnReset)

Parameters

Name	Type	Details
appPackage	string	name of app
appActivity	string	name of activity
appWaitPackage optional	string	name of app to wait for
appWaitActivity optional	string	name of activity to wait for
intentAction=android.intent.action.MAIN optional	string	intent action which will be used to start activity
intentCategory=android.intent.category.LAUNCHER optional	string	intent category which will be used to start activity
intentFlags=0x10200000 optional	string	flags that will be used to start activity
optionalIntentArguments optional	string	additional intent arguments that will be used to start activity
dontStopAppOnReset optional	string	doesn’t stop the process of the app under test, before starting the app using adb

Support

---

appiumGetSystemBars

Retrieve visibility and bounds information of the status and navigation bars. This is the raw Appium protocol endpoint. Prefer the getSystemBars mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getSystemBars mobile command (driver.getSystemBars()) instead

Usage

driver.appiumGetSystemBars()

Returns

• <object[]> systemBars: Information about visibility and bounds of status and navigation bar

Support

---

getDeviceTime

Get the time on the device.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getDeviceTime()

Returns

• <string> time: Time on the device

Support

---

appiumGetDisplayDensity

Get display density from device. This is the raw Appium protocol endpoint. Prefer the getDisplayDensity mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getDisplayDensity mobile command (driver.getDisplayDensity()) instead

Usage

driver.appiumGetDisplayDensity()

Returns

• <*>

Support

---

appiumTouchId

Simulate a touch id event (iOS Simulator only). To enable this feature, the allowTouchIdEnroll desired capability must be set to true and the Simulator must be enrolled. When you set allowTouchIdEnroll to true, it will set the Simulator to be enrolled by default. The enrollment state can be toggled. This call will only work if Appium process or its parent application (e.g. Terminal.app or Appium.app) has access to Mac OS accessibility in System Preferences > Security & Privacy > Privacy > Accessibility list.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the touchId mobile command (driver.touchId()) instead

Usage

driver.appiumTouchId(match)

Parameters

Name	Type	Details
match	boolean	are we simulating a successful touch (true) or a failed touch (false)

Support

---

appiumToggleEnrollTouchId

Toggle the simulator being enrolled to accept touchId (iOS Simulator only). To enable this feature, the allowTouchIdEnroll desired capability must be set to true. When allowTouchIdEnroll is set to true the Simulator will be enrolled by default, and the 'Toggle Touch ID Enrollment' changes the enrollment state. This call will only work if the Appium process or its parent application (e.g., Terminal.app or Appium.app) has access to Mac OS accessibility in System Preferences > Security & Privacy > Privacy > Accessibility list.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the toggleEnrollTouchId mobile command (driver.toggleEnrollTouchId()) instead

Usage

driver.appiumToggleEnrollTouchId(enabled)

Parameters

Name	Type	Details
enabled=true optional	boolean	equals to true if TouchID enrollment should be enabled

Support

---

appiumLaunchApp

Launch an app on device. This is the raw Appium protocol endpoint. Prefer the launchApp mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the launchApp mobile command (driver.launchApp()) instead

Usage

driver.appiumLaunchApp()

Support

---

appiumCloseApp

Close an app on device. This is the raw Appium protocol endpoint. Prefer the closeApp mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the closeApp mobile command (driver.closeApp()) instead

Usage

driver.appiumCloseApp()

Support

---

appiumBackground

Send the currently running app for this session to the background. This is the raw Appium protocol endpoint. Prefer the background mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the background mobile command (driver.background()) instead

Usage

driver.appiumBackground(seconds)

Parameters

Name	Type	Details
seconds=null	number, null	Timeout after which to restore the app. A value of -1 disables the timeout

Support

---

endCoverage

Get test coverage data.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.execute('mobile: shell', { ... }) instead

Usage

driver.endCoverage(intent, path)

Parameters

Name	Type	Details
intent	string	intent to broadcast
path	string	path to .ec file

Support

---

appiumGetStrings

Get app strings. This is the raw Appium protocol endpoint. Prefer the getStrings mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getStrings mobile command (driver.getStrings()) instead

Usage

driver.appiumGetStrings(language, stringFile)

Parameters

Name	Type	Details
language optional	string	language code
stringFile optional	string	path to the string file

Returns

• <object> appStrings: all defined Strings from an app for the specified language and strings filename

Support

---

setValueImmediate

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.addValue(...) or driver.setValue(...) instead

Usage

driver.setValueImmediate(elementId, text)

Parameters

Name	Type	Details
elementId	String	the id of an element returned in a previous call to Find Element(s)
text	string	text to set to an element

Support

---

replaceValue

Replace the value to element directly.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.addValue(...) or driver.setValue(...) instead

Usage

driver.replaceValue(elementId, value)

Parameters

Name	Type	Details
elementId	String	the id of an element returned in a previous call to Find Element(s)
value	string	value to replace on element

Support

---

getSettings

Retrieve the current session settings.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getSettings()

Returns

• <object> settings: JSON hash of all the currently specified settings, see Settings API

Support

---

updateSettings

Update the session settings.

Appium command. More details can be found in the official protocol docs.

Usage

driver.updateSettings(settings)

Parameters

Name	Type	Details
settings	object	key/value object with settings to update

Support

---

receiveAsyncResponse

Callback url for asynchronous execution of JavaScript.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.executeAsyncScript(...) instead

Usage

driver.receiveAsyncResponse(response)

Parameters

Name	Type	Details
response	object	response to receive on device

Support

---

appiumGsmCall

Make GSM call (Emulator only). This is the raw Appium protocol endpoint. Prefer the gsmCall mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the gsmCall mobile command (driver.gsmCall()) instead

Usage

driver.appiumGsmCall(phoneNumber, action)

Parameters

Name	Type	Details
phoneNumber	string	the phone number to call to
action	string	The action - 'call', 'accept', 'cancel', 'hold'

Support

---

appiumGsmSignal

Set GSM signal strength (Emulator only). This is the raw Appium protocol endpoint. Prefer the gsmSignal mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the gsmSignal mobile command (driver.gsmSignal()) instead

Usage

driver.appiumGsmSignal(signalStrength, signalStrengh)

Parameters

Name	Type	Details
signalStrength	string	signal strength in the range [0, 4]
signalStrengh optional	string	signal strength in the range [0, 4]. Please also set this parameter with the same value if you use Appium v1.11.0 or lower (see https://github.com/appium/appium/issues/12234).

Support

---

appiumPowerCapacity

Set the battery percentage (Emulator only). This is the raw Appium protocol endpoint. Prefer the powerCapacity mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the powerCapacity mobile command (driver.powerCapacity()) instead

Usage

driver.appiumPowerCapacity(percent)

Parameters

Name	Type	Details
percent	number	percentage value in range [0, 100]

Support

---

appiumPowerAC

Set the state of the battery charger to connected or not (Emulator only). This is the raw Appium protocol endpoint. Prefer the powerAC mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the powerAC mobile command (driver.powerAC()) instead

Usage

driver.appiumPowerAC(state)

Parameters

Name	Type	Details
state	string	set the state. on or off

Support

---

appiumGsmVoice

Set GSM voice state (Emulator only). This is the raw Appium protocol endpoint. Prefer the gsmVoice mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the gsmVoice mobile command (driver.gsmVoice()) instead

Usage

driver.appiumGsmVoice(state)

Parameters

Name	Type	Details
state	string	state of GSM voice - 'unregistered', 'home', 'roaming', 'searching', 'denied', 'off', 'on'

Support

---

appiumSendSms

Simulate an SMS message (Emulator only). This is the raw Appium protocol endpoint. Prefer the sendSms mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the sendSms mobile command (driver.sendSms()) instead

Usage

driver.appiumSendSms(phoneNumber, message)

Parameters

Name	Type	Details
phoneNumber	string	the phone number to send the SMS too
message	string	the SMS message

Support

---

appiumFingerPrint

Authenticate users by using their finger print scans on supported emulators. This is the raw Appium protocol endpoint. Prefer the fingerPrint mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the fingerPrint mobile command (driver.fingerPrint()) instead

Usage

driver.appiumFingerPrint(fingerprintId)

Parameters

Name	Type	Details
fingerprintId	number	finger prints stored in Android Keystore system (from 1 to 10)

Support

---

appiumSetClipboard

Set the content of the system clipboard. This is the raw Appium protocol endpoint. Prefer the setClipboard mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the setClipboard mobile command (driver.setClipboard()) instead

Usage

driver.appiumSetClipboard(content, contentType, label)

Parameters

Name	Type	Details
content	string	The actual base64 encoded clipboard content
contentType optional	string	The type of the content to get. Plaintext, Image, URL. Android supports only plaintext
label optional	string	Clipboard data label for Android

Returns

• <string> response: Response from Appium server

Support

---

appiumGetClipboard

Get the content of the system clipboard. This is the raw Appium protocol endpoint. Prefer the getClipboard mobile command which provides automatic Appium 3 compatibility with fallback for older drivers.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use the getClipboard mobile command (driver.getClipboard()) instead

Usage

driver.appiumGetClipboard(contentType)

Parameters

Name	Type	Details
contentType optional	string	The type of the content to get. Plaintext, Image, URL. Android supports only plaintext

Returns

• <string> response: Clipboard content as base64-encoded string or an empty string if the clipboard is empty

Support

---

touchPerform

This functionality is only available from within a native context. 'Touch Perform' works similarly to the other singular touch interactions, except that this allows you to chain together more than one touch action as one command. This is useful because Appium commands are sent over the network and there's latency between commands. This latency can make certain touch interactions impossible because some interactions need to be performed in one sequence. Vertical, for example, requires pressing down, moving to a different y coordinate, and then releasing. For it to work, there can't be a delay between the interactions.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) instead

Usage

driver.touchPerform(actions)

Parameters

Name	Type	Details
actions	object[]	The type of action to perform (e.g. moveTo, release, press, tap, wait)

Example

// do a horizontal swipe by percentage
const startPercentage = 10;
const endPercentage = 90;
const anchorPercentage = 50;

const { width, height } = driver.getWindowSize();
const anchor = height * anchorPercentage / 100;
const startPoint = width * startPercentage / 100;
const endPoint = width * endPercentage / 100;
driver.touchPerform([
  {
    action: 'press',
    options: {
      x: startPoint,
      y: anchor,
    },
  },
  {
    action: 'wait',
    options: {
      ms: 100,
    },
  },
  {
    action: 'moveTo',
    options: {
      x: endPoint,
      y: anchor,
    },
  },
  {
    action: 'release',
    options: {},
  },
]);

Support

---

multiTouchPerform

This functionality is only available from within a native context. Perform a multi touch action sequence.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) instead

Usage

driver.multiTouchPerform(actions)

Parameters

Name	Type	Details
actions	object[]	The type of action to perform (e.g. moveTo, release, press, tap, wait)

Support

---

executeDriverScript

Execute a script in a child process. This approach helps minimize potential latency associated with each command. Using this command in Appium 2 or later requires installing the execute-driver plugin.

Appium command. More details can be found in the official protocol docs.

Usage

driver.executeDriverScript(script, type, timeout)

Parameters

Name	Type	Details
script	string	The script to execute. It has access to a 'driver' object which represents a WebdriverIO session attached to the current server.
type optional	string	The language/framework used in the script. Currently, only 'webdriverio' is supported and is the default.
timeout optional	number	The number of milliseconds the script should be allowed to run before being killed by the Appium server. Defaults to the equivalent of 1 hour.

Returns

• <object> result: An object containing two fields: 'result', which is the return value of the script itself, and 'logs', which contains 3 inner fields, 'log', 'warn', and 'error', which hold an array of strings logged by console.log, console.warn, and console.error in the script's execution.

---

getEvents

Get events logged in the current session.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getEvents(type)

Parameters

Name	Type	Details
type optional	string, string[]	One or more event types to filter the returned events

Returns

• <object> result: A JSON hash of events like {'commands' => [{'cmd' => 123455, ....}], 'startTime' => 1572954894127, }.

Support

---

logEvent

Log a custom event.

Appium command. More details can be found in the official protocol docs.

Usage

driver.logEvent(vendor, event)

Parameters

Name	Type	Details
vendor	string	Name of the namespace (vendor) used to prefix the event
event	string	Name of the event

Support

---

compareImages

Compare two images using the specified mode of comparison. Using this command in Appium 2 or later requires installing the images plugin.

Appium command. More details can be found in the official protocol docs.

Usage

driver.compareImages(mode, firstImage, secondImage, options)

Parameters

Name	Type	Details
mode	string	One of possible comparison modes: 'matchFeatures', 'getSimilarity', 'matchTemplate'.
firstImage	string	Base64-encoded image file.
secondImage	string	Base64-encoded image file.
options=[object Object] optional	object	The supported values of this property depend on the mode value. See Appium documentation for more details.

Returns

• <object> result: The content of the resulting dictionary depends on the mode and options values. See Appium documentation for more details.

---

implicitWait

Set the amount of time the driver should wait when searching for elements. When searching for a single element, the driver should poll the page until an element is found or the timeout expires, whichever occurs first. When searching for multiple elements, the driver should poll the page until at least one element is found or the timeout expires, at which point it should return an empty list. If this command is never sent, the driver should default to an implicit wait of 0ms.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.setTimeouts(...) instead

Usage

driver.implicitWait(ms)

Parameters

Name	Type	Details
ms	number	The amount of time, in milliseconds, to wait on an element.

Support

---

getLocationInView

Determine an element's location on the screen once it has been scrolled into view.

Note: This is considered an internal command and should only be used to determine an element's location for correctly generating native events.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.getElementRect(...) or element.getLocation() instead

Usage

driver.getLocationInView(elementId)

Parameters

Name	Type	Details
elementId	String	ID of the element to route the command to

Returns

• <Object> location: The X and Y coordinates for the element on the page.

Support

---

sendKeys

Send a sequence of key strokes to the active element

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with keyUp and keyDown actions instead

Usage

driver.sendKeys(value)

Parameters

Name	Type	Details
value	string[]	The sequence of keys to type. An array must be provided.

Support

---

availableIMEEngines

List all available IME engines on the device. To use an engine, it has to be present in this list.

Appium command. More details can be found in the official protocol docs.

Usage

driver.availableIMEEngines()

Returns

• <String[]> engines: A list of available engines

Support

---

getActiveIMEEngine

Get the name of the active IME engine. The name string is platform specific.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getActiveIMEEngine()

Returns

• <String> engine: The name of the active IME engine

Support

---

isIMEActivated

Indicates whether IME input is active at the moment

Appium command. More details can be found in the official protocol docs.

Usage

driver.isIMEActivated()

Returns

• <Boolean> isActive: true if IME input is available and currently active, false otherwise

Support

---

deactivateIMEEngine

De-activates the currently-active IME engine.

Appium command. More details can be found in the official protocol docs.

Usage

driver.deactivateIMEEngine()

Support

---

activateIMEEngine

Activates an IME engine.

Appium command. More details can be found in the official protocol docs.

Usage

driver.activateIMEEngine(engine)

Parameters

Name	Type	Details
engine	string	name of the engine to activate

Support

---

asyncScriptTimeout

Set the amount of time, in milliseconds, that asynchronous scripts executed by /session/:sessionId/execute_async are permitted to run before they are aborted and a Timeout error is returned to the client.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.setTimeouts(...) instead

Usage

driver.asyncScriptTimeout(ms)

Parameters

Name	Type	Details
ms	number	The amount of time, in milliseconds, that time-limited commands are permitted to run

Support

---

submit

Submit a form element.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Please explicitly find and click the submit element

Usage

driver.submit(elementId)

Parameters

Name	Type	Details
elementId	String	ID of the form element to be submitted

Support

---

getElementSize

Determine an element's size in pixels. The size will be returned as a JSON object with width and height properties.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.getElementRect(...) or element.getSize() instead

Usage

driver.getElementSize(elementId)

Parameters

Name	Type	Details
elementId	String	ID of the element to route the command to

Returns

• <Object> size: The width and height of the element, in pixels.

Support

---

getElementLocation

Determine an element's location on the page. The point (0, 0) refers to the upper-left corner of the page. The element's coordinates are returned as a JSON object with x and y properties.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.getElementRect(...) or element.getLocation() instead

Usage

driver.getElementLocation(elementId)

Parameters

Name	Type	Details
elementId	String	ID of the element to route the command to

Returns

• <Object> location: The X and Y coordinates for the element on the page.

Support

---

touchClick

Single tap on the touch enabled device.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with pointerDown and pointerUp actions instead

Usage

driver.touchClick(element)

Parameters

Name	Type	Details
element	string	ID of the element to single tap on.

Support

---

touchDown

Finger down on the screen.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with a pointerDown action instead

Usage

driver.touchDown(x, y)

Parameters

Name	Type	Details
x	number	x coordinate on the screen
y	number	y coordinate on the screen

Support

---

touchUp

Finger up on the screen.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with a pointerUp action instead

Usage

driver.touchUp(x, y)

Parameters

Name	Type	Details
x	number	x coordinate on the screen
y	number	y coordinate on the screen

Support

---

touchMove

Finger move on the screen.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with a pointerMove action instead

Usage

driver.touchMove(x, y)

Parameters

Name	Type	Details
x	number	x coordinate on the screen
y	number	y coordinate on the screen

Support

---

touchLongClick

Long press on the touch screen using finger motion events.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with pointerDown, pause and pointerUp actions instead

Usage

driver.touchLongClick(element)

Parameters

Name	Type	Details
element	string	ID of the element to long press on

Support

---

touchFlick

Flick on the touch screen using finger motion events. This flick command starts at a particular screen location.

Appium command. More details can be found in the official protocol docs.

caution

This protocol command is deprecated
Use driver.performActions(...) with pointerDown, pointerMove and pointerUp actions instead

Usage

driver.touchFlick(xoffset, yoffset, element, speed, xspeed, yspeed)

Parameters

Name	Type	Details
xoffset optional	number	the x offset in pixels to flick by
yoffset optional	number	the y offset in pixels to flick by
element optional	string	ID of the element where the flick starts
speed optional	number	the speed in pixels per seconds
xspeed optional	number	the x speed in pixels per second
yspeed optional	number	the y speed in pixels per second

Support

---

getOrientation

Get the current device orientation.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getOrientation()

Returns

• <String> orientation: The current orientation corresponding to a value defined in ScreenOrientation: LANDSCAPE|PORTRAIT.

Support

---

setOrientation

Set the device orientation

Appium command. More details can be found in the official protocol docs.

Usage

driver.setOrientation(orientation)

Parameters

Name	Type	Details
orientation	string	the new browser orientation as defined in ScreenOrientation: LANDSCAPE|PORTRAIT

Support

---

getGeoLocation

Get the current geo location.

Appium command. More details can be found in the official protocol docs.

Usage

driver.getGeoLocation()

Returns

• <Object> location: The current geo location.

---

setGeoLocation

Set the current geo location.

Appium command. More details can be found in the official protocol docs.

Usage

driver.setGeoLocation(location)

Parameters

Name	Type	Details
location	object	the new location ({latitude: number, longitude: number, altitude: number})