info: → POST /wd/hub/session {“desiredCapabilities”:{“browserName”:“Chrome”,“platformName”:“Android”,“version”:“8.0”,“deviceName”:“Sham_Emulator”},“requiredCapabilities”:{},“capabilities”:{“desiredCapabilities”:{“browserName”:“Chrome”,“platformName”:“Android”,“version”:“8.0”,“deviceName”:“Sham_Emulator”},“requiredCapabilities”:{},“alwaysMatch”:{“browserName”:“Chrome”,“platformName”:“Android”},“firstMatch”:}}
info: Client User-Agent string: Apache-HttpClient/4.5.3 (Java/1.8.0_111)
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. : version
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session db1d5dfb-2b2a-479b-aae9-057009b44f06
info: [debug] Checking whether adb is present
info: [debug] Using adb from C:\Users\shamsundar\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\shamsundar.br\AppData\Local\Android\sdk\platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device emulator-5554
info: [debug] Setting device id to emulator-5554
info: [debug] Waiting for device to be ready and to respond to shell commands (timeout = 5)
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 wait-for-device
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Pushing unlock helper app to device…
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 install “C:\Program Files (x86)\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “dumpsys window”
info: [debug] Screen already unlocked, continuing.
info: [debug] Forwarding system:4724 to device:4724
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 forward tcp:4724 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: C:\Users\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 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\shamsundar\AppData\Local\Android\sdk\platform-tools\adb.exe -s emulator-5554 shell “ps ‘uiautomator’”
info: [debug] Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Command failed:
info: [debug] Error: Command failed:
at ChildProcess.exithandler (child_process.js:637:15)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Process.ChildProcess._handle.onexit (child_process.js:810:5)
info: [debug] Responding to client with error: {“status”:33,“value”:{“message”:“A new session could not be created. (Original error: Command failed: )”,“killed”:false,“code”:1,“signal”:null,“origValue”:"Command failed: "},“sessionId”:null}
info: ← POST /wd/hub/session 500 3640.530 ms - 192