I’d like to run Appium tests on a Crosswalk-Cordova application,and I am running into not being able to switch to WebView with that setup. Here are my Appium logs:
debug: Available contexts: NATIVE_APP,WEBVIEW_com.alpinemetrics
debug: ["WEBVIEW_com.alpinemetrics"]
debug: Available contexts: NATIVE_APP,WEBVIEW_com.alpinemetrics
debug: Connecting to chrome-backed webview
debug: Creating Chrome session
debug: Ensuring Chromedriver exists
debug: Killing any old chromedrivers, running: FOR /F "usebackq tokens=5" %a in (`netstat -nao ^| findstr /R /C:"9515 "`
) do (FOR /F "usebackq" %b in (`TASKLIST /FI "PID eq %a" ^| findstr /I chromedriver.exe`) do (IF NOT %b=="" TASKKILL /F
/PID %b))
debug: No old chromedrivers seemed to exist
debug: Spawning chromedriver with: C:\Users\Anna\AppData\Roaming\npm\node_modules\appium\build\chromedriver\windows\chro
medriver.exe
debug: [CHROMEDRIVER] Starting ChromeDriver (v2.9.248315) on port 9515
debug: Making http request with opts: {"url":"http://127.0.0.1:9515/wd/hub/session","method":"POST","json":{"sessionId":
null,"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.alpinemetrics","androidUseRunningApp":true,"androidDe
viceSerial":"01ac52e99616a284"}}}}
debug: Didn't get a new command in 60 secs, shutting down...
info: Shutting down appium session
debug: Pressing the HOME button
debug: executing: "C:\Workspace\Eclipse\sdk\platform-tools\adb.exe" -s 01ac52e99616a284 shell "input keyevent 3"
debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: Cleaning up Chromedriver
debug: Killing chromedriver
debug: Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while pro
cessing the command. (Original error: read ECONNRESET)","code":"ECONNRESET","errno":"ECONNRESET","syscall":"read","origV
alue":"read ECONNRESET"},"sessionId":"02adcf26-0609-4f30-ae92-9e6c61deb435"}
info: <-- POST /wd/hub/session/02adcf26-0609-4f30-ae92-9e6c61deb435/context 500 60917.808 ms - 276
debug: Chromedriver exited with code null
Has anyone run into this problem and found a solution? Could it be that there is no support for Crosswalk apps yet?
EDIT: I upgraded chromedriver to 2.10, and I am getting a new error:
Chrome version must be >= 33.0.1750.0
The chrome version in our crosswalk app is 36.
Is there a known bug with crosswalk where chrome version isn’t getting recognized correctly?
Appium logs related to the issue:
debug: Spawning chromedriver with: C:\Users\Anna\AppData\Roaming\npm\node_modules\appium\build\chromedriver\windows\chro
medriver.exe
debug: [CHROMEDRIVER] Starting ChromeDriver (v2.10.267521) on port 9515
Only local connections are allowed.
debug: Making http request with opts: {"url":"http://127.0.0.1:9515/wd/hub/session","method":"POST","json":{"sessionId":
null,"desiredCapabilities":{"chromeOptions":{"androidPackage":"com.alpinemetrics","androidUseRunningApp":true,"androidDe
viceSerial":"01ac52e99616a284"}}}}
error: Chromedriver create session did not work. Status was 200 and body was {"sessionId":"7578d4305d459157db12043bd3e24
4ca","status":13,"value":{"message":"unknown error: Chrome version must be >= 33.0.1750.0\n (Driver info: chromedriver=
2.10.267521,platform=Windows NT 6.3 x86_64)"}}