hi people,
i hope you could give me a hand with that.
since 3 days ago i’m having issues trying to create webdriver session agains any device i try to use.
i’m using these caps to connect to a specific android 6.0 device
{“desiredCapabilities”:{“chromeOptions”:{“androidPackage”
:“com.android.chrome”,“androidDeviceSerial”:“0876a1dd255da2a0”}}}
and get this log
info: Welcome to Appium v1.4.16 (REV ae6877eff263066b26328d457bd285c0cc62430d)
info: Appium REST http interface listener started on 0.0.0.0:5001
info: [debug] Non-default server args: {“udid”:“0876a1dd255da2a0”,“port”:5001,“b
ootstrapPort”:6001,“chromeDriverPort”:6501}
info: Console LogLevel: debug
info: --> POST /wd/hub/session {“desiredCapabilities”:{“deviceName”:“0876a1dd255
da2a0”,“platformName”:“Android”,“platformVersion”:“6.0”,“browserName”:“chrome”}}
info: Client User-Agent string: undefined
info: Set mode: Proxying straight through to Chromedriver
info: [debug] Looks like we want chrome on android
info: [debug] Creating new appium session 684a89ad-4175-43af-bcf3-5b41060f5a2d
info: [debug] Checking whether adb is present
info: [debug] Using adb from C:\Users\mgatica\AppData\Local\Android\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 alr
eady 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\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe devices
info: [debug] 1 device(s) connected
info: Found device 0876a1dd255da2a0
info: [debug] Setting device id to 0876a1dd255da2a0
info: [debug] Waiting for device to be ready and to respond to shell commands (t
imeout = 5)
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 wait-for-device
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 shell “echo ‘ready’”
info: [debug] Starting logcat capture
info: [debug] Pushing unlock helper app to device…
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 install “C:\Users\mgatica\AppData\Roa
ming\npm\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk”
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 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\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 shell “getprop ro.build.version.sdk”
info: [debug] Device is at API Level 23
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 shell “am start -S -a android.intent.
action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n io.appium.unloc
k/.Unlock”
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 shell “dumpsys window”
info: [debug] Screen is unlocked, continuing
info: [debug] Forwarding system:6001 to device:4724
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 forward tcp:6001 tcp:4724
info: [debug] Pushing appium bootstrap to device…
info: [debug] executing cmd: C:\Users\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 push “C:\Users\mgatica\AppData\Ro
aming\npm\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\mgatica\AppData\Local\Android\android-sdk
platform-tools\adb.exe -s 0876a1dd255da2a0 shell “ps ‘uiautomator’”
info: [debug] No matching processes found
info: [debug] Running bootstrap
info: [debug] spawning: C:\Users\mgatica\AppData\Local\Android\android-sdk\platf
orm-tools\adb.exe -s 0876a1dd255da2a0 shell uiautomator runtest AppiumBootstrap.
jar -c io.appium.android.bootstrap.Bootstrap -e pkg com.android.chrome -e disabl
eAndroidWatchers false
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
info: [debug] [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRun
ner
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.andro
id.bootstrap.Bootstrap
info: [debug] [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
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] [BOOTSTRAP] [debug] Got data from client: {“cmd”:“action”,“action”
:“getDataDir”,“params”:{}}
info: [debug] dataDir set to: /data/local/tmp
info: Chromedriver: Changed state to ‘starting’
info: [debug] [BOOTSTRAP] [debug] Got command of type ACTION
info: [debug] [BOOTSTRAP] [debug] Got command action: getDataDir
info: [debug] [BOOTSTRAP] [debug] Returning result: {“status”:0,“value”:"/data
/local/tmp"}
info: Chromedriver: Set chromedriver binary as: C:\Users\mgatica\AppData\Roaming
\npm\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chrom
edriver.exe
info: Chromedriver: Killing any old chromedrivers, running: FOR /F “usebackq tok
ens=5” %a in (netstat -nao ^| findstr /R /C:"6501 ") 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:\Users\mgatica\AppData\Roaming
\npm\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chrom
edriver.exe --url-base=wd/hub --port=6501
info: Chromedriver: [STDOUT] Starting ChromeDriver 2.18.343845 (73dd713ba7fbfb73
cbb514e62641d8c96a94682a) on port 6501
Only local connections are allowed.
info: JSONWP Proxy: Proxying [GET /status] to [GET http://127.0.0.1:6501/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”,“n
ame”:“Windows NT”,“version”:“6.1 SP1”}}}”
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:6501/wd/h
ub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”
:“com.android.chrome”,“androidDeviceSerial”:“0876a1dd255da2a0”}}}
info: [debug] [BOOTSTRAP] [debug] Emitting system alert message
info: [debug] Emitting alert message…
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“ebae438ece5681b5
206bf014c042e89a”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driv
er info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),pla
tform=W…
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:6501/wd/h
ub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”
:“com.android.chrome”,“androidDeviceSerial”:“0876a1dd255da2a0”}}}
info: [debug] [BOOTSTRAP] [debug] Emitting system alert message
info: [debug] Emitting alert message…
info: JSONWP Proxy: Got response with status 200: {“sessionId”:“4ec977cfec91199d
f4b336ccc0104628”,“status”:100,“value”:{“message”:"chrome not reachable\n (Driv
er info: chromedriver=2.18.343845 (73dd713ba7fbfb73cbb514e62641d8c96a94682a),pla
tform=W…
info: JSONWP Proxy: Proxying [POST /session] to [POST http://127.0.0.1:6501/wd/h
ub/session] with body: {“desiredCapabilities”:{“chromeOptions”:{“androidPackage”
:“com.android.chrome”,“androidDeviceSerial”:“0876a1dd255da2a0”}}}
info: [debug] [BOOTSTRAP] [debug] Emitting system alert message
info: [debug] Emitting alert message…
about my environment is a win 7
appium -v 1.4.16
node -v v4.2.2
npm -v 2.14.7
appium-doctor
Running Android Checks
? ANDROID_HOME is set to “C:\Users\mgatica\AppData\Local\Android\android-sdk”
? JAVA_HOME is set to “C:\Program Files\Java\jdk1.8.0_11.”
? ADB exists at C:\Users\mgatica\AppData\Local\Android\android-sdk\platform-tool
s\adb.exe
? Android exists at C:\Users\mgatica\AppData\Local\Android\android-sdk\tools\and
roid.bat
? Emulator exists at C:\Users\mgatica\AppData\Local\Android\android-sdk\tools\em
ulator.exe
? Android Checks were successful.
? All Checks were successful
thanks to any tip you could bring me about.