Edgars Eglītis
Edgars Eglītis
Closing due to no response
Issue can be resolved by using the gesture editor in the Actions tab.
Did the above fix resolve this issue? I will close this for now, but will reopen if the issue is still relevant.
Closing this since the resetApp action has now been removed.
Closing due to no response
Closing due to no response
I think the Java client updates have been covered in #1157, so I am closing this.
`cross-env` for `watch:browser` has been added in #943.
Issue may be caused by the provided combination of `appium:app` and `appium:appPackage`, without `appium:appActivity`. I would probably suggest using either _only_ `appium:app`, or `appium:appPackage` _and_ `appium:appActivity`. See the [UiAutomator2 documentation...
The simplest solution that I can suggest here is to launch the Appium server with the flag `--allow-insecure chromedriver_autodownload`. For more information on hybrid mode in Appium 2, see the...