Appium chrome driver seems not working with Chrome for Android version 54

The problem

Appium chrome driver seems not working with Chrome for Android version 54. The browsing is not working

Environment

• Appium version 1.4.16.1:
• Last Appium version that did not exhibit the issue 1.4.16.1: (towards another Android phone with Chrome 53)
• Desktop OS/version used to run Appium: Windows
• Mobile platform/version under test: Android 4.2.2
• Real device or emulator/simulator: Real device
• Appium CLI or Appium.app|exe: Appium.exe

Details

Describe in more detail the problem you have been experiencing, if necessary.

Link to Appium logs

`

Launching Appium server with command: C:\Program Files (x86)\Appium\node.exe lib\server\main.js --address 127.0.0.1 --port 4723 --platform-name Android --platform-version 23 --automation-name Appium --log-no-color info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d) info: Appium REST http interface listener started on 127.0.0.1:4723 info: [debug] Non-default server args: {“address”:“127.0.0.1”,“logNoColors”:true,“platformName”:“Android”,“platformVersion”:“23”,“automationName”:“Appium”} info: Console LogLevel: debug info: --> POST /wd/hub/session {“desiredCapabilities”:{“newCommandTimeout”:“600”,“browserName”:“Chrome”,“udid”:“FA31JW100457”,“platformName”:“Android”,“deviceName”:“Android”,“enablePerformanceLogging”:true,“platform”:“ANDROID”}} info: Client User-Agent string: Apache-HttpClient/4.5.2 (Java/1.8.0_72) info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : platform info: Set mode: Proxying straight through to Chromedriver info: [debug] Looks like we want chrome on android info: [debug] Creating new appium session c567d2bc-6900-4000-b944-081645400e78 info: [debug] Checking whether adb is present info: [debug] Using adb from C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe info: [debug] Using fast reset? true info: [debug] Preparing device for session info: [debug] Not checking whether app is present since we are assuming it’s already on the device info: Retrieving device info: [debug] Trying to find a connected android device info: [debug] Getting connected devices… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe devices info: [debug] 1 device(s) connected info: Found device FA31JW100457 info: [debug] Setting device id to FA31JW100457 info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5) info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 wait-for-device info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “echo ‘ready’” info: [debug] Starting logcat capture info: [debug] Pushing unlock helper app to device… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk” info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “dumpsys window” info: Unlocking screen info: [debug] Screen is locked, trying to unlock info: [debug] Getting device API level info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “getprop ro.build.version.sdk” info: [debug] Device is at API Level 17 info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n io.appium.unlock/.Unlock” info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “dumpsys window” info: [debug] Screen is unlocked, continuing info: [debug] Forwarding system:4724 to device:4724 info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 forward tcp:4724 tcp:4724 info: [debug] Pushing appium bootstrap to device… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/ info: Starting App info: [debug] Attempting to kill all ‘uiautomator’ processes info: [debug] Getting all processes with ‘uiautomator’ info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “ps ‘uiautomator’” info: [debug] No matching processes found info: [debug] Running bootstrap info: [debug] spawning: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.android.chrome -e disableAndroidWatchers false info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream= info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap: info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1 info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724 info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready info: [debug] [BOOTSTRAP] [debug] Loading json… info: [debug] [BOOTSTRAP] [debug] Registered crash watchers. info: [debug] Pushing command to appium work queue: [“getDataDir”,{}] info: [debug] [BOOTSTRAP] [debug] Client connected info: [debug] dataDir set to: /data/local/tmp info: Chromedriver: Changed state to ‘starting’ info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}} info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“/data/local/tmp”,“status”:0} info: Chromedriver: Set chromedriver binary as: C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe info: Chromedriver: 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 %a)) info: Chromedriver: No old chromedrivers seemed to exist info: Chromedriver: Spawning chromedriver with: C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe --url-base=wd/hub --port=9515 info: Chromedriver: [STDOUT] Starting ChromeDriver 2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a) on port 9515 Only local connections are allowed. info: JSONWP Proxy: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body info: JSONWP Proxy: Got response with status 200: “{"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x86_64","name":"Windows NT","version":"6.1 SP1"}}}” info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“FA31JW100457”},“loggingPrefs”:{“performance”:“ALL”}}} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“c032fa5ced3b26a1624666c278b8b459”,“status”:33,“value”:{“message”:“session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData… info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“FA31JW100457”},“loggingPrefs”:{“performance”:“ALL”}}} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“18db8beb01f76e431ce1e6fa280e95c9”,“status”:33,“value”:{“message”:“session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData… info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“FA31JW100457”},“loggingPrefs”:{“performance”:“ALL”}}} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“1203d026fbd620e567e5a53a8b2a36bb”,“status”:33,“value”:{“message”:“session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData… info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“FA31JW100457”},“loggingPrefs”:{“performance”:“ALL”}}} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“eebecba51f97ea473d6f8a317379aab2”,“status”:33,“value”:{“message”:“session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData… error: Chromedriver: Chromedriver exited unexpectedly with code null, signal SIGTERM info: Chromedriver: Changed state to ‘stopped’ info: Chromedriver stopped unexpectedly on us, shutting down then calling back up with the on-die callback error: Chromedriver: Error: A new session could not be created. (Original error: session not created exception from unknown error: Runtime.executionContextCreated has invalid ‘context’: {“auxData”:{“frameId”:“10406.1”,“isDefault”:true},“id”:1,“name”:””,“origin”:“😕/”} (Session info: chrome=54.0.2840.68) (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)) at JWProxy.command$ (lib/proxy.js:133:15) at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\regenerator\runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke](C:Program Files %28x86%29Appiumnode_modulesappiumnode_modulesappium-chromedrivernode_modulesappium-jsonwp-proxynode_modulesbabel-runtimeregeneratorruntime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next](C:Program Files %28x86%29Appiumnode_modulesappiumnode_modulesappium-chromedrivernode_modulesappium-jsonwp-proxynode_modulesbabel-runtimeregeneratorruntime.js💯21) at GeneratorFunctionPrototype.invoke (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\regenerator\runtime.js:136:37) at bound (domain.js:284:14) at GeneratorFunctionPrototype.runBound (domain.js:297:12) at run (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules\es6.promise.js:89:39) at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules\es6.promise.js💯28 at flush (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules$.microtask.js:17:13) at process._tickDomainCallback (node.js:381:11) { [Error: A new session could not be created. (Original error: session not created exception from unknown error: Runtime.executionContextCreated has invalid ‘context’: {“auxData”:{“frameId”:“10406.1”,“isDefault”:true},“id”:1,“name”:””,“origin”:“😕/”} (Session info: chrome=54.0.2840.68) (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64))] status: 33, value: { message: ‘session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid 'context': {“auxData”:{“frameId”:“10406.1”,“isDefault”:true},“id”:1,“name”:“”,“origin”:“😕/”}\n (Session info: chrome=54.0.2840.68)\n (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)’ }, httpCode: 200 } error: Failed to start an Appium session, err was: Error: A new session could not be created. (Original error: session not created exception from unknown error: Runtime.executionContextCreated has invalid ‘context’: {“auxData”:{“frameId”:“10406.1”,“isDefault”:true},“id”:1,“name”:“”,“origin”:“😕/”} (Session info: chrome=54.0.2840.68) (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)) info: [debug] Cleaning up appium session info: [debug] Error: A new session could not be created. (Original error: session not created exception from unknown error: Runtime.executionContextCreated has invalid ‘context’: {“auxData”:{“frameId”:“10406.1”,“isDefault”:true},“id”:1,“name”:“”,“origin”:“😕/”} (Session info: chrome=54.0.2840.68) (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)) at JWProxy.command$ (lib/proxy.js:133:15) at tryCatch (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\regenerator\runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke](C:Program Files %28x86%29Appiumnode_modulesappiumnode_modulesappium-chromedrivernode_modulesappium-jsonwp-proxynode_modulesbabel-runtimeregeneratorruntime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as next](C:Program Files %28x86%29Appiumnode_modulesappiumnode_modulesappium-chromedrivernode_modulesappium-jsonwp-proxynode_modulesbabel-runtimeregeneratorruntime.js💯21) at GeneratorFunctionPrototype.invoke (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\regenerator\runtime.js:136:37) at bound (domain.js:284:14) at GeneratorFunctionPrototype.runBound (domain.js:297:12) at run (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules\es6.promise.js:89:39) at C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules\es6.promise.js💯28 at flush (C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\node_modules\appium-jsonwp-proxy\node_modules\babel-runtime\node_modules\core-js\library\modules$.microtask.js:17:13) at process._tickDomainCallback (node.js:381:11) info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: A new session could not be created. (Original error: session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData":{"frameId":"10406.1","isDefault":true},"id":1,"name":"","origin":"😕/"}\n (Session info: chrome=54.0.2840.68)\n (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)))”,“status”:33,“value”:{“message”:“session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData":{"frameId":"10406.1","isDefault":true},"id":1,"name":"","origin":"😕/"}\n (Session info: chrome=54.0.2840.68)\n (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64)”},“httpCode”:200,“origValue”:“A new session could not be created. (Original error: session not created exception\nfrom unknown error: Runtime.executionContextCreated has invalid ‘context’: {"auxData":{"frameId":"10406.1","isDefault":true},"id":1,"name":"","origin":"😕/"}\n (Session info: chrome=54.0.2840.68)\n (Driver info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),platform=Windows NT 6.1 SP1 x86_64))”},“sessionId”:null} info: <-- POST /wd/hub/session 500 29334.221 ms - 1378 info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”} info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“status”:0} info: [debug] [BOOTSTRAP] [debug] Closed client connection info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=. info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream= info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=. info: [debug] [UIAUTOMATOR STDOUT] Time: 24.065 info: [debug] [UIAUTOMATOR STDOUT] OK (1 test) info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1 info: [debug] Sent shutdown command, waiting for UiAutomator to stop… info: [debug] UiAutomator shut down normally info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s FA31JW100457 shell “am force-stop com.android.chrome” info: [debug] Stopping logcat capture info: [debug] Logcat terminated with code null, signal SIGTERM info: [debug] Cleaning up appium session info: --> POST /wd/hub/session {“desiredCapabilities”:{“newCommandTimeout”:“600”,“browserName”:“Chrome”,“udid”:“HT245W112303”,“platformName”:“Android”,“deviceName”:“Android”,“enablePerformanceLogging”:true,“platform”:“ANDROID”}} info: Client User-Agent string: Apache-HttpClient/4.5.2 (Java/1.8.0_72) info: [debug] The following desired capabilities were provided, but not recognized by appium. They will be passed on to any other services running on this server. : platform info: Set mode: Proxying straight through to Chromedriver info: [debug] Looks like we want chrome on android info: [debug] Creating new appium session 522ef3b6-eaae-444d-bdcb-45a71c854eb2 info: [debug] Checking whether adb is present info: [debug] Using adb from C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe info: [debug] Using fast reset? true info: [debug] Preparing device for session info: [debug] Not checking whether app is present since we are assuming it’s already on the device info: Retrieving device info: [debug] Trying to find a connected android device info: [debug] Getting connected devices… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe devices info: [debug] 1 device(s) connected info: Found device HT245W112303 info: [debug] Setting device id to HT245W112303 info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5) info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 wait-for-device info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “echo ‘ready’” info: [debug] Starting logcat capture info: [debug] Pushing unlock helper app to device… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk” info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “dumpsys window” info: Unlocking screen info: [debug] Screen is locked, trying to unlock info: [debug] Getting device API level info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “getprop ro.build.version.sdk” info: [debug] Device is at API Level 17 info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n io.appium.unlock/.Unlock” info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “dumpsys window” info: [debug] Screen is unlocked, continuing info: [debug] Forwarding system:4724 to device:4724 info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 forward tcp:4724 tcp:4724 info: [debug] Pushing appium bootstrap to device… info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 push “C:\Program Files (x86)\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar” /data/local/tmp/ info: Starting App info: [debug] Attempting to kill all ‘uiautomator’ processes info: [debug] Getting all processes with ‘uiautomator’ info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “ps ‘uiautomator’” info: [debug] No matching processes found info: [debug] Running bootstrap info: [debug] spawning: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.android.chrome -e disableAndroidWatchers false info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream= info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap: info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1 info: [debug] [BOOTSTRAP] [debug] Socket opened on port 4724 info: [debug] [BOOTSTRAP] [debug] Appium Socket Server Ready info: [debug] [BOOTSTRAP] [debug] Loading json… info: [debug] [BOOTSTRAP] [debug] Registered crash watchers. info: [debug] Pushing command to appium work queue: [“getDataDir”,{}] info: [debug] [BOOTSTRAP] [debug] Client connected info: [debug] dataDir set to: /data/local/tmp info: Chromedriver: Changed state to ‘starting’ info: Chromedriver: Set chromedriver binary as: C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe info: Chromedriver: 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 %a)) info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”:“getDataDir”,“params”:{}} info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“/data/local/tmp”,“status”:0} info: Chromedriver: No old chromedrivers seemed to exist info: Chromedriver: Spawning chromedriver with: C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe --url-base=wd/hub --port=9515 info: Chromedriver: [STDOUT] Starting ChromeDriver 2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a) on port 9515 Only local connections are allowed. info: JSONWP Proxy: Proxying [GET /status] to [GET http://127.0.0.1:9515/wd/hub/status] with no body info: JSONWP Proxy: Got response with status 200: “{"sessionId":"","status":0,"value":{"build":{"version":"alpha"},"os":{"arch":"x86_64","name":"Windows NT","version":"6.1 SP1"}}}” info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:9515/wd/hub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“HT245W112303”},“loggingPrefs”:{“performance”:“ALL”}}} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:{“acceptSslCerts”:true,“applicationCacheEnabled”:false,“browserConnectionEnabled”:false,“browserName”:“chrome”,“chrome”:{},"cssSel… info: Chromedriver: Changed state to ‘online’ info: [debug] Overriding session id with “6594ff1345b83437dfc0e478535e234b” info: [debug] Device launched! Ready for commands info: [debug] Setting command timeout to 600 secs info: [debug] Appium session started with sessionId 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session 303 13865.510 ms - 70 info: --> GET /wd/hub/session/6594ff1345b83437dfc0e478535e234b {} info: JSONWP Proxy: Proxying [GET /wd/hub/session/6594ff1345b83437dfc0e478535e234b] to [GET http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b] with body: {} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:{“acceptSslCerts”:true,“applicationCacheEnabled”:false,“browserConnectionEnabled”:false,“browserName”:“chrome”,“chrome”:{},"cssSel… info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- GET /wd/hub/session/6594ff1345b83437dfc0e478535e234b 200 8.496 ms - 529 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/timeouts {“type”:“page load”,“ms”:120000} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/timeouts] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/timeouts] with body: {“type”:“page load”,“ms”:120000} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:null} info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/timeouts 200 46.213 ms - 72 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/url {“url”:“http://www.imdb.com”} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/url] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/url] with body: {“url”:“http://www.imdb.com”} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:null} info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/url 200 13825.654 ms - 72 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute {“script”:“return document.readyState”,“args”:[]} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] with body: {“script”:“return document.readyState”,“args”:[]} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:“complete”} info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute 200 52.521 ms - 78 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute {“script”:“var performance = window.performance || {};var timing = performance.timing || {};return timing;”,“args”:[]} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] with body: {“script”:“var performance = window.performance || {};var timing = performance.timing || {};return timing;”,“args”:[]} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:{“connectEnd”:1477478846752,“connectStart”:1477478846632,“domComplete”:1477478859730,“domContentLoadedEventEnd”:1477478853402,“dom… info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute 200 45.799 ms - 679 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/log {“type”:“performance”} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/log] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/log] with body: {“type”:“performance”} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:[{“level”:“INFO”,“message”:”{"message":{"method":"Page.frameAttached","params":{"frameId":"12395.2","parentFrameId":… info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/log 200 142.097 ms - 834425 info: --> POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute {“script”:“var performance = window.performance || {};var timings = performance.getEntriesByType(‘resource’) || {};return timings;”,“args”:[]} info: JSONWP Proxy: Proxying [POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] to [POST http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute] with body: {“script”:“var performance = window.performance || {};var timings = performance.getEntriesByType(‘resource’) || {};return timings;”,“args”:[]} info: JSONWP Proxy: Got response with status 200: {“sessionId”:“6594ff1345b83437dfc0e478535e234b”,“status”:0,“value”:[{“connectEnd”:0,“connectStart”:0,“domainLookupEnd”:0,“domainLookupStart”:0,“duration”:207.895,“entryType”:“resource”,“fetchStart”… info: JSONWP Proxy: Replacing sessionId 6594ff1345b83437dfc0e478535e234b with 6594ff1345b83437dfc0e478535e234b info: <-- POST /wd/hub/session/6594ff1345b83437dfc0e478535e234b/execute 200 140.770 ms - 51600 info: --> DELETE /wd/hub/session/6594ff1345b83437dfc0e478535e234b {} info: Shutting down appium session info: Chromedriver: Changed state to ‘stopping’ info: JSONWP Proxy: Proxying [DELETE /] to [DELETE http://127.0.0.1:9515/wd/hub/session/6594ff1345b83437dfc0e478535e234b] with no body info: JSONWP Proxy: Got response with status 200: “{"sessionId":"6594ff1345b83437dfc0e478535e234b","status":0,"value":null}” info: Chromedriver: Changed state to ‘stopped’ info: [debug] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“shutdown”} info: [debug] [BOOTSTRAP] [debug] Got command of type SHUTDOWN info: [debug] [BOOTSTRAP] [debug] Returning result: {“value”:“OK, shutting down”,“status”:0} info: [debug] [BOOTSTRAP] [debug] Closed client connection info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=. info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0 info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream= info: [debug] [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=. info: [debug] [UIAUTOMATOR STDOUT] Time: 24.684 info: [debug] [UIAUTOMATOR STDOUT] OK (1 test) info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1 info: [debug] Sent shutdown command, waiting for UiAutomator to stop… info: [debug] UiAutomator shut down normally info: [debug] executing cmd: C:\Users\user\AppData\Local\Android\sdk\platform-tools\adb.exe -s HT245W112303 shell “am force-stop com.android.chrome” info: [debug] Stopping logcat capture info: [debug] Logcat terminated with code null, signal SIGTERM info: [debug] Cleaning up appium session info: [debug] Responding to client with success: {“status”:0,“value”:null,“sessionId”:“6594ff1345b83437dfc0e478535e234b”} info: <-- DELETE /wd/hub/session/6594ff1345b83437dfc0e478535e234b 200 1958.114 ms - 72 {“status”:0,“value”:null,“sessionId”:“6594ff1345b83437dfc0e478535e234b”} `

[LakshmiManohar]

Appium chrome driver working with Chrome for Android version 54- Test Pass

• Appium version 1.4.16.1
• Chrome: 54.0.2840.68
• Desktop OS/version used to run Appium: Windows
• Mobile platform/version under test: Android 6.0.1
• Real device or emulator/simulator: Real device
• Appium CLI or Appium.app|exe: Appium.exe

https://chromedriver.storage.googleapis.com/index.html?path=2.25/ : Chrome Driver Version 2.25.426923

Replace the old Chrome driver with new downloaded chrome driver in your local drive C:\Program Files (x86)\Appium\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\

– # @yhzs8 #

[yhzs8]

@tonyaveniros your issue is not exactly the same: For you the chrome driver is too new for the chrome version. (either downgrade chrome driver or upgrade chrome). For me the chrome driver was too old for the chrome version. (either upgrade chrome driver or downgrade chrome).