You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add chromedriverExecutableDir and autodownload support (#48)
* feat: add chromedriverExecutableDir and autodownload support
* set browser from UA if the browser was an empty
* fix bad reference
* add JSON.stringify
* Update README.md
Co-authored-by: Jonathan Lipps <[email protected]>
---------
Co-authored-by: Jonathan Lipps <[email protected]>
Copy file name to clipboardexpand all lines: README.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,8 @@ package in your `package.json`)
36
36
|`appium:appId`|[Required] The app package ID, if you want Appium to use an app already on the TV. Exclusive with `appium:app`|
37
37
|`appium:app`|[Optional] An absolute path to your `.ipk` app file, if you want Appium to install the app.|
38
38
|`appium:debuggerPort`|[Optional; default `9998`] The port on the device exposed for remote Chromium debugging.|
39
-
|`appium:chromedriverExecutable`|[Optional] Most LG TVs run a very old version of Chrome. Because this driver uses Chromedriver under the hood, you'll need to have a very old version of Chromedriver handy that works with the version of Chrome backing the apps on your TV. In our testing, we've found Chromedriver 2.36 to work with most TVs. You need to tell the driver where you've installed this version of Chromedriver using the `appium:chromedriverExecutable` capability, passing in an absolute path to the Chromedriver binary.|
39
+
|`appium:chromedriverExecutable`(*)|[Optional] Most LG TVs run a very old version of Chrome. Because this driver uses Chromedriver under the hood, you'll need to have a very old version of Chromedriver handy that works with the version of Chrome backing the apps on your TV. In our testing, we've found Chromedriver 2.36 to work with most TVs. You need to tell the driver where you've installed this version of Chromedriver using the `appium:chromedriverExecutable` capability, passing in an absolute path to the Chromedriver binary.|
40
+
|`appium:chromedriverExecutableDir`(*) |[Optional] Full path to the folder where chromedriver executables are located. This folder is used then to store the downloaded chromedriver executables if automatic download is enabled with `chromedriver_autodownload` security flag. Please read [Automatic Discovery of Compatible Chromedriver in appium-uiautomator2-driver](https://github.com/appium/appium-uiautomator2-driver?tab=readme-ov-file#automatic-discovery-of-compatible-chromedriver) for more details. |
40
41
|`appium:websocketPort`|[Optional; default `3000`] The websocket port on the device exposed for remote control|
41
42
|`appium:websocketPortSecure`|[Optional; default `3001`] The secure websocket port on the device exposed for remote control|
42
43
|`appium:useSecureWebsocket`|[Optional; default `false`] Flag that enables use of `websocketPortSecure` port, also starts WebSocket over https instead. **DISCLAIMER** Enabling this flag, it is required to set environment variable `export NODE_TLS_REJECT_UNAUTHORIZED=0`, which can be a potential security risk. A new session request might get `unable to get local issuer certificate` error message.|
@@ -49,6 +50,9 @@ package in your `package.json`)
49
50
|`appium:rcMode`|[Optional; default `js`; must be `rc` or `js`] When the value is `js`, the `webos: pressKey` command will operate with JS executed via Chromedriver. Otherwise, keys will be sent using the websocket remote control API. Note that when `appium:remoteOnly` is set to true, the value of `appium:rcMode` will always behave as if set to `rc`.|
50
51
|`appium:keyCooldown`|[Optional; default `750`] How long to wait in between remote key presses|
51
52
53
+
(*) `appium:chromedriverExecutable` or `appium:chromedriverExecutableDir` are required. The chromedriver autodwonload works only when `appium:chromedriverExecutableDir` is provided.
54
+
If both capabilities are given, `appium:chromedriverExecutableDir` will take priority.
55
+
52
56
## Supported Commands
53
57
54
58
These are the WebDriver (and extension) commands supported by this driver. Note that in its normal
0 commit comments