Getting error while running test case on windows as Did not get session redirect from Chromedriver

hi all,
i am getting this error while running my java testcase
at first time it ran successfully afterwards its not running and

here is the log which is generated

info: Welcome to Appium v1.2.3 (REV 90d746b373f55e8653a251d2ce8c62df37941919)
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,“androidDeviceReadyTimeout”:“40”,“platformName”:“Android”,“platformVersion”:“18”,“automationName”:“Appium”}
info: Console LogLevel: debug
info: e[37m–>e[39m e[37mPOSTe[39m e[37m/wd/hub/sessione[39m e[90m{“desiredCapabilities”:{“platformVersion”:“4.3”,“deviceName”:“Android”,“platformName”:“Android”,“browserName”:“Chrome”}}e[39m
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session 518b7fa7-cc7c-43be-8560-73ff7cbf395d
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: [debug] Checking whether adb is present
info: [debug] Using adb from C:\AndroidSetup\platform-tools\adb.exe
info: Retrieving device
info: [debug] Trying to find a connected android device
info: [debug] Getting connected devices…
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” devices
info: [debug] 1 device(s) connected
info: Found device E8AZCY237063
info: [debug] Setting device id to E8AZCY237063
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 40)
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 wait-for-device
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Pushing unlock helper app to device…
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 install “C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 shell “dumpsys window”
info: [debug] Writing dumpsys output to C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium.dumpsys.log
info: [debug] Screen already unlocked, continuing.
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 push “C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\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: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 shell “ps ‘uiautomator’”
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: C:\AndroidSetup\platform-tools\adb.exe -s E8AZCY237063 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1e[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunnere[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrape[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=e[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:e[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1e[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServere[39m
info: [debug] e[90m[UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1e[39m
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] Pushing command to appium work queue: [“getDataDir”,{}]
info: [debug] [BOOTSTRAP] [debug] Registered crash watchers.
info: [debug] [BOOTSTRAP] [debug] Client connected
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: [debug] dataDir set to: /data/local/tmp
info: [debug] Creating Chrome session
info: [debug] Set chromedriver binary as: C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] Ensuring Chromedriver exists
info: [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))
info: [debug] No old chromedrivers seemed to exist
info: [debug] Spawning chromedriver with: C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] [CHROMEDRIVER] Starting ChromeDriver (v2.10.267521) on port 9515
Only local connections are allowed.
info: [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.android.chrome”,“androidDeviceSerial”:"E8AZCY237063”}}}}
info: [debug] [CHROMEDRIVER STDERR] [0.004][SEVERE]: Could not bind socket to 127.0.0.1:9515
info: [debug] [CHROMEDRIVER] Port not available. Exiting…
info: [debug] Chromedriver exited with code 1
info: [debug] Getting connected devices…
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 devices
error: Chromedriver create session did not work. Status was 200 and body was {“sessionId”:“56651cae714e33035a278a03df0e2dcc”,“status”:13,“value”:{“message”:“unknown error: Device E8AZCY237063 is already in use\n (Driver info: chromedriver=2.10.267521,platform=Windows NT 6.1 SP1 x86_64)”}}
error: Failed to start an Appium session, err was: Error: Did not get session redirect from Chromedriver
info: [debug] Error: Did not get session redirect from Chromedriver
at null. (C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\lib\devices\android\chromedriver.js:220:12)
at Request._callback (C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\lib\devices\common.js:116:5)
at Request.self.callback (C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\node_modules\request\request.js:121:22)
at Request.EventEmitter.emit (events.js:98:17)
at Request. (C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\node_modules\request\request.js:985:14)
at Request.EventEmitter.emit (events.js:117:20)
at IncomingMessage. (C:\Users\sinsfm\Desktop\AppiumForWindows-1.2.3.1\Appium\node_modules\appium\node_modules\request\request.js:936:12)
at IncomingMessage.EventEmitter.emit (events.js:117:20)
at _stream_readable.js:920:16
at process._tickDomainCallback (node.js:459:13)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Did not get session redirect from Chromedriver)”,“origValue”:“Did not get session redirect from Chromedriver”},“sessionId”:null}
info: e[37m<-- POST /wd/hub/session e[39me[31m500e[39me[90m 2364.674 ms - 214e[39m e[90me[39m
info: [debug] 1 device(s) connected
info: [debug] executing: “C:\AndroidSetup\platform-tools\adb.exe” -s E8AZCY237063 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

Hi,

Even i am facing similar issue. I find that first appium creates a session 84e17df7-895e-446c-b9e8-2e0c720bd979 and then chromedriver overrides the session with b586e49810904aea23dbeec91694de7f
At end, new sessionid is deleted but the old sessionid that was created by appium does not have any reference and thus creates problem related to device release.

I am looking for some solution where

  1. either i can run use the same sessionid i.e avoid chromedriver override the original session
  2. run chromedriver on same port 4723 instead of 9515
  3. close all the sessions at the end

info: --> POST /wd/hub/session {“desiredCapabilities”:{“platformVersion”:“4.3”,"
orientation":“LANDSCAPE”,“app”:“chrome”,“deviceName”:“4d00b81de1133037”,“platfor
mName”:“Android”,“browserName”:“chrome”,“deviceCategory”:“phone”,“version”:“4.3”
}}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {“desiredCapabilities”:{“platformVersion”:"
4.3",“orientation”:“LANDSCAPE”,“app”:“chrome”,“deviceName”:“4d00b81de1133037”,“p
latformName”:“Android”,“browserName”:“chrome”,“deviceCategory”:“phone”,“version”
:“4.3”}}
debug: The following desired capabilities were provided, but not recognized by a
ppium. They will be passed on to any other services running on this server. : de
viceCategory, version
debug: Looks like we want chrome on android
debug: Creating new appium session 84e17df7-895e-446c-b9e8-2e0c720bd979
debug: Preparing device for session
debug: Not checking whether app is present since we are assuming it’s already on
the device
debug: Checking whether adb is present
debug: Using adb from E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702
\sdk\platform-tools\adb.exe
info: Retrieving device
debug: Trying to find a connected android device
debug: Getting connected devices…
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” devices
debug: 1 device(s) connected
info: Found device 4d00b81de1133037
debug: Setting device id to 4d00b81de1133037
debug: Waiting for device to be ready and to respond to shell commands (timeout
= 5)
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” -s 4d00b81de1133037 wait-for-device
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” -s 4d00b81de1133037 shell “echo ‘ready’”
debug: Starting logcat capture
debug: Pushing unlock helper app to device…
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” -s 4d00b81de1133037 install “E:\Dev-setup\AppiumForWin
dows-1.2.0.1\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” -s 4d00b81de1133037 shell “dumpsys window”
debug: Writing dumpsys output to E:\Dev-setup\AppiumForWindows-1.2.0.1\Appium\no
de_modules\appium.dumpsys.log
debug: Screen already unlocked, continuing.
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: E:\Dev-setup\AppiumForWindows-1.2.0.1\Appium
node_modules\appium\build\chromedriver\windows\chromedriver.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/sessi
on”,“method”:“POST”,“json”:{“sessionId”:null,“desiredCapabilities”:{“chromeOptio
ns”:{“androidPackage”:“com.android.chrome”,“androidDeviceSerial”:“4d00b81de11330
37”}}}}
debug: Successfully started chrome session
debug: Overriding session id with “b586e49810904aea23dbeec91694de7f”
debug: Device launched! Ready for commands
debug: Setting command timeout to the default of 60 secs
debug: Appium session started with sessionId b586e49810904aea23dbeec91694de7f
info: <-- POST /wd/hub/session 303 9315.080 ms - 9
info: --> GET /wd/hub/session/b586e49810904aea23dbeec91694de7f {}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f
debug: Request received with params: {}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f”,“method”:“GET”}
debug: Proxied response received with status 200: “{“sessionId”:“b586e4981090
4aea23dbeec91694de7f”,“status”:0,“value”:{“acceptSslCerts”:true,“applica
tionCacheEnabled”:false,“browserConnectionEnabled”:false,“browserName”:“ch
rome”,“chrome”:{},“cssSelectorsEnabled”:true,“databaseEnabled”:false,“ha
ndlesAlerts”:true,“javascriptEnabled”:true,“locationContextEnabled”:true,”
nativeEvents":true,“platform”:“ANDROID”,“rotatable”:false,“takesHeapSnap
shot”:true,“takesScreenshot”:true,“version”:“37.0.2062.117”,“webStorageE
nabled”:true}}"
info: <-- GET /wd/hub/session/b586e49810904aea23dbeec91694de7f 200 13.145 ms - 4
76
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/url {“url”:“http
s://myturbotax.intuit.com/”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/url
debug: Request received with params: {“url”:“https://myturbotax.intuit.com/”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/url”,“method”:“POST”,“json”:{“url”:“https://
myturbotax.intuit.com/”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:null}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/url 200 5550.895
ms - 72
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/execute {“args”:
[],“script”:“return navigator.userAgent”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/execute
debug: Request received with params: {“args”:[],“script”:“return navigator.userA
gent”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/execute”,“method”:“POST”,“json”:{“args”:[],"
script":“return navigator.userAgent”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:“Mozilla/5.0 (Linux; Android 4.3; GT-I9500
Build/JSS15J) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.117 Mobile
Safari/537.36”}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/execute 200 1662
.834 ms - 206
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/timeouts/implici
t_wait {“ms”:10000}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/timeouts/implicit_wait
debug: Request received with params: {“ms”:10000}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/timeouts/implicit_wait”,“method”:“POST”,“jso
n”:{“ms”:10000}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:null}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/timeouts/implici
t_wait 200 11.910 ms - 72
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element {“using”
:“id”,“value”:“ius-userid”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element
debug: Request received with params: {“using”:“id”,“value”:“ius-userid”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element”,“method”:“POST”,“json”:{“using”:"id
",“value”:“ius-userid”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:{“ELEMENT”:“0.04667960782535374-1”}}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element 200 1860
.358 ms - 103
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-1/value {“id”:“0.04667960782535374-1”,“value”:[“parveen_gupta@intuit
.com”]}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element/0.04667960782535374-1/value
debug: Request received with params: {“id”:“0.04667960782535374-1”,“value”:[“par
[email protected]”]}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element/0.04667960782535374-1/value”,"method
":“POST”,“json”:{“id”:“0.04667960782535374-1”,“value”:["[email protected]
"]}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:null}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-1/value 200 1741.133 ms - 72
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element {“using”
:“id”,“value”:“ius-password”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element
debug: Request received with params: {“using”:“id”,“value”:“ius-password”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element”,“method”:“POST”,“json”:{“using”:"id
",“value”:“ius-password”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:{“ELEMENT”:“0.04667960782535374-2”}}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element 200 130.
357 ms - 103
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-2/value {“id”:“0.04667960782535374-2”,“value”:[“helloworld”]}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element/0.04667960782535374-2/value
debug: Request received with params: {“id”:“0.04667960782535374-2”,“value”:[“hel
loworld”]}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element/0.04667960782535374-2/value”,"method
":“POST”,“json”:{“id”:“0.04667960782535374-2”,“value”:[“helloworld”]}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:null}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-2/value 200 1430.295 ms - 72
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element {“using”
:“id”,“value”:“ius-sign-in-submit-btn”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element
debug: Request received with params: {“using”:“id”,“value”:“ius-sign-in-submit-b
tn”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element”,“method”:“POST”,“json”:{“using”:"id
",“value”:“ius-sign-in-submit-btn”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:{“ELEMENT”:“0.04667960782535374-3”}}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element 200 139.
596 ms - 103
info: --> POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-3/click {“id”:“0.04667960782535374-3”}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f/element/0.04667960782535374-3/click
debug: Request received with params: {“id”:“0.04667960782535374-3”}
debug: Proxying command to 127.0.0.1:9515
debug: Making http request with opts: {“url”:“http://127.0.0.1:9515/wd/hub/sessi
on/b586e49810904aea23dbeec91694de7f/element/0.04667960782535374-3/click”,“method
“:“POST”,“json”:{“id”:“0.04667960782535374-3”}}
debug: Proxied response received with status 200: {“sessionId”:“b586e49810904aea
23dbeec91694de7f”,“status”:0,“value”:null}
info: <-- POST /wd/hub/session/b586e49810904aea23dbeec91694de7f/element/0.046679
60782535374-3/click 200 2811.178 ms - 72
info: --> DELETE /wd/hub/session/b586e49810904aea23dbeec91694de7f {}
debug: Appium request initiated at /wd/hub/session/b586e49810904aea23dbeec91694d
e7f
debug: Request received with params: {}
info: Shutting down appium session
debug: Killing chromedriver
debug: Chromedriver exited with code null
debug: (killed by signal SIGTERM)
debug: executing: “E:\Dev-setup\AndroidSDK\adt-bundle-windows-x86_64-20140702\sd
k\platform-tools\adb.exe” -s 4d00b81de1133037 shell “am force-stop com.android.c
hrome”
debug: Cleaning up appium session
debug: Responding to client with success: {“status”:0,“value”:null,“sessionId”:”
b586e49810904aea23dbeec91694de7f”}
info: <-- DELETE /wd/hub/session/b586e49810904aea23dbeec91694de7f 200 905.317 ms

  • 72 {“status”:0,“value”:null,“sessionId”:“b586e49810904aea23dbeec91694de7f”}

delete chromedriver.exe from Task Manager