class: Android
- since: v1.9
- langs: js
Playwright has experimental support for Android automation. This includes Chrome for Android and Android WebView.
Requirements
- Android device or AVD Emulator.
- ADB daemon running and authenticated with your device. Typically running
adb devicesis all you need to do. Chrome 87or newer installed on the device- "Enable command line on non-rooted devices" enabled in
chrome://flags.
Known limitations
- Raw USB operation is not yet supported, so you need ADB.
- Device needs to be awake to produce screenshots. Enabling "Stay awake" developer mode will help.
- We didn't run all the tests against the device, so not everything works.
How to run
An example of the Android automation script would be:
const { _android: android } = require('playwright');
(async () => {
// Connect to the device.
const [device] = await android.devices();
console.log(`Model: ${device.model()}`);
console.log(`Serial: ${device.serial()}`);
// Take screenshot of the whole device.
await device.screenshot({ path: 'device.png' });
{
// --------------------- WebView -----------------------
// Launch an application with WebView.
await device.shell('am force-stop org.chromium.webview_shell');
await device.shell('am start org.chromium.webview_shell/.WebViewBrowserActivity');
// Get the WebView.
const webview = await device.webView({ pkg: 'org.chromium.webview_shell' });
// Fill the input box.
await device.fill({
res: 'org.chromium.webview_shell:id/url_field',
}, 'github.com/microsoft/playwright');
await device.press({
res: 'org.chromium.webview_shell:id/url_field',
}, 'Enter');
// Work with WebView's page as usual.
const page = await webview.page();
await page.waitForNavigation({ url: /.*microsoft\/playwright.*/ });
console.log(await page.title());
}
{
// --------------------- Browser -----------------------
// Launch Chrome browser.
await device.shell('am force-stop com.android.chrome');
const context = await device.launchBrowser();
// Use BrowserContext as usual.
const page = await context.newPage();
await page.goto('https://webkit.org/');
console.log(await page.evaluate(() => window.location.href));
await page.screenshot({ path: 'page.png' });
await context.close();
}
// Close the device.
await device.close();
})();
async method: Android.connect
- since: v1.28
- returns: <[AndroidDevice]>
This methods attaches Playwright to an existing Android device.
Use [method: Android.launchServer] to launch a new Android server instance.
param: Android.connect.endpoint
- since: v1.28
endpoint<[string]>
A browser websocket endpoint to connect to.
option: Android.connect.headers
- since: v1.28
headers<[Object]<[string], [string]>>
Additional HTTP headers to be sent with web socket connect request. Optional.
option: Android.connect.slowMo
- since: v1.28
slowMo<[float]>
Slows down Playwright operations by the specified amount of milliseconds. Useful so that you
can see what is going on. Defaults to 0.
option: Android.connect.timeout
- since: v1.28
timeout<[float]>
Maximum time in milliseconds to wait for the connection to be established. Defaults to
30000 (30 seconds). Pass 0 to disable timeout.
async method: Android.devices
- since: v1.9
- returns: <[Array]<[AndroidDevice]>>
Returns the list of detected Android devices.
option: Android.devices.host
- since: v1.22
host<[string]>
Optional host to establish ADB server connection. Default to 127.0.0.1.
option: Android.devices.port
- since: v1.20
port<[int]>
Optional port to establish ADB server connection. Default to 5037.
option: Android.devices.omitDriverInstall
- since: v1.21
omitDriverInstall<[boolean]>
Prevents automatic playwright driver installation on attach. Assumes that the drivers have been installed already.
async method: Android.launchServer
- since: v1.28
- langs: js
- returns: <[BrowserServer]>
Launches Playwright Android server that clients can connect to. See the following example:
Usage
Server Side:
const { _android } = require('playwright');
(async () => {
const browserServer = await _android.launchServer({
// If you have multiple devices connected and want to use a specific one.
// deviceSerialNumber: '<deviceSerialNumber>',
});
const wsEndpoint = browserServer.wsEndpoint();
console.log(wsEndpoint);
})();
Client Side:
const { _android } = require('playwright');
(async () => {
const device = await _android.connect('<wsEndpoint>');
console.log(device.model());
console.log(device.serial());
await device.shell('am force-stop com.android.chrome');
const context = await device.launchBrowser();
const page = await context.newPage();
await page.goto('https://webkit.org/');
console.log(await page.evaluate(() => window.location.href));
await page.screenshot({ path: 'page-chrome-1.png' });
await context.close();
})();
option: Android.launchServer.adbHost
- since: v1.28
adbHost<[string]>
Optional host to establish ADB server connection. Default to 127.0.0.1.
option: Android.launchServer.adbPort
- since: v1.28
adbPort<[int]>
Optional port to establish ADB server connection. Default to 5037.
option: Android.launchServer.omitDriverInstall
- since: v1.28
omitDriverInstall<[boolean]>
Prevents automatic playwright driver installation on attach. Assumes that the drivers have been installed already.
option: Android.launchServer.deviceSerialNumber
- since: v1.28
deviceSerialNumber<[string]>
Optional device serial number to launch the browser on. If not specified, it will throw if multiple devices are connected.
option: Android.launchServer.host
- since: v1.45
host<[string]>
Host to use for the web socket. It is optional and defaults to localhost, accepting connections only from the loopback interface. Pass an explicit address (e.g. 0.0.0.0) to accept connections from the network — be aware this exposes the device RPC to anything that can reach the listening port.
option: Android.launchServer.port
- since: v1.28
port<[int]>
Port to use for the web socket. Defaults to 0 that picks any available port.
option: Android.launchServer.wsPath
- since: v1.28
wsPath<[string]>
Path at which to serve the Android Server. For security, this defaults to an unguessable string.
:::warning
Any process or web page (including those running in Playwright) with knowledge
of the wsPath can take control of the OS user. For this reason, you should
use an unguessable token when using this option.
:::
method: Android.setDefaultTimeout
- since: v1.9
This setting will change the default maximum time for all the methods accepting [param: timeout] option.
param: Android.setDefaultTimeout.timeout
- since: v1.9
timeout<[float]>
Maximum time in milliseconds
Source: docs/src/mobile-api/class-android.md