Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chrome not reachable error when trying to automate android hybrid app on windows using emulator. #3584

Closed
himanshushekhar opened this issue Sep 8, 2014 · 3 comments
Closed

Chrome not reachable error when trying to automate android hybrid app on windows using emulator. #3584

himanshushekhar opened this issue Sep 8, 2014 · 3 comments
Assignees
@imurchie

Comments

@himanshushekhar
Copy link

Hello,

I just started to use Appium for one of my hybrid app for android and am stuck with this error for quite a while now. I have looked through many similar issues and tried their solution but none worked for me. I am using Android 4.4.2 with chrome, 31.0.1650.59 installed in it and chromedriver version is 2.10.289383. I have changed the file permissions of /data/local to 777 as well. Here are the details:

My capabilities:

    capabilities.setCapability("deviceName", "Default");
    capabilities.setCapability("platformName", "Android");
    capabilities.setCapability(CapabilityType.BROWSER_NAME, "");
    capabilities.setCapability(CapabilityType.VERSION, "4.4.2");
    capabilities.setCapability(CapabilityType.PLATFORM, "WINDOWS");
    capabilities.setCapability("appPackage",
            "com.example.sampleclient");
    capabilities.setCapability("appActivity", "MainActivity");
    capabilities.setCapability("app", app.getAbsolutePath());
    driver = new AppiumDriver(new URL("http://127.0.0.1:4723/wd/hub"),
            capabilities);
    driver.manage().timeouts().implicitlyWait(80, TimeUnit.SECONDS);

Appium log

Starting Node Server

info: Welcome to Appium v1.2.0 (REV e53f49c)
debug: Non-default server args: {"address":"127.0.0.1","fullReset":true,"logNoColors":true,"platformName":"Android","platformVersion":"19","automationName":"Appium"}
info: Appium REST http interface listener started on 127.0.0.1:4723
info: LogLevel: debug
info: --> POST /wd/hub/session {"desiredCapabilities":{"platform":"WINDOWS","app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","browserName":"","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"}}
debug: Appium request initiated at /wd/hub/session
debug: Request received with params: {"desiredCapabilities":{"platform":"WINDOWS","app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","browserName":"","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"}}
info: Starting android appium
debug: Using local app from desired caps: E:\Tools\SampleClient.apk
debug: Creating new appium session 3ae80c73-0c82-4c9e-81e8-628c270d0ad6
info: Retrieving device
debug: Using fast reset? false
debug: Preparing device for session
debug: Checking whether app is actually present
debug: Checking whether adb is present
debug: Using adb from E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe
debug: Trying to find a connected android device
debug: Getting connected devices...
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" devices
debug: 1 device(s) connected
info: Found device emulator-5554
debug: Setting device id to emulator-5554
debug: Waiting for device to be ready and to respond to shell commands (timeout = 5)
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 wait-for-device
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "echo 'ready'"
debug: Starting logcat capture
debug: Parsing package and activity from app manifest
debug: Checking whether aapt is present
debug: Using aapt from E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\aapt.exe
debug: packageAndLaunchActivityFromManifest: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\aapt.exe" dump badging E:\Tools\SampleClient.apk
debug: badging package: com.example.sampleclient

debug: badging act: com.example.sampleclient
.MainActivity
debug: Parsed package and activity are: com.example.sampleclient
/com.example.sampleclient
.MainActivity
debug: Getting device API level
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "getprop ro.build.version.sdk"
debug: Device is at API Level 19
info: Device API level is: 19
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "getprop persist.sys.language"
debug: Current device language: en
debug: java -jar "E:\Tools\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar" "E:\Tools\SampleClient.apk" "C:\Windows\Temp\com.example.sampleclient
" en
debug: No strings.xml for language 'en', getting default strings.xml
debug: java -jar "E:\Tools\Appium\node_modules\appium\node_modules\appium-adb\jars\strings_from_apk.jar" "E:\Tools\SampleClient.apk" "C:\Windows\Temp\com.example.sampleclient
"
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 push "C:\Windows\Temp\com.example.sampleclient
\strings.json" /data/local/tmp
debug: Checking whether aapt is present
debug: Using aapt from E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\aapt.exe
debug: processFromManifest: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\aapt.exe" dump xmltree "E:\Tools\SampleClient.apk" AndroidManifest.xml
debug: Set app process to: com.example.sampleclient

debug: Uninstalling com.example.sampleclient

debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "am force-stop com.example.sampleclient
"
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 uninstall com.example.sampleclient

debug: App was not uninstalled, maybe it wasn't on device?
debug: Checking app cert for E:\Tools\SampleClient.apk: java -jar "E:\Tools\Appium\node_modules\appium\node_modules\appium-adb\jars\verify.jar" "E:\Tools\SampleClient.apk"
debug: App already signed.
debug: Zip-aligning E:\Tools\SampleClient.apk
debug: Checking whether zipalign is present
debug: Using zipalign from E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\zipalign.exe
debug: zipAlignApk: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\zipalign.exe" -f 4 "E:\Tools\SampleClient.apk" "C:\Users\HIMANS~1\AppData\Local\Temp\appium11488-9488-mu7fgt.tmp"
debug: MD5 for app is 1b2f6ed8f30d9463df6dfb0920d67367
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "ls /data/local/tmp/1b2f6ed8f30d9463df6dfb0920d67367.apk"
debug: Getting install status for com.example.sampleclient

debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "pm list packages -3 com.example.sampleclient
"
info: Installing App
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "mkdir -p /data/local/tmp/"
debug: Removing any old apks
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "ls /data/local/tmp/*.apk"
debug: Found an apk we want to keep at /data/local/tmp/1b2f6ed8f30d9463df6dfb0920d67367.apk
debug: Couldn't find any apks to remove
debug: Uninstalling com.example.sampleclient

debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "am force-stop com.example.sampleclient
"
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 uninstall com.example.sampleclient

debug: App was not uninstalled, maybe it wasn't on device?
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "pm install -r /data/local/tmp/1b2f6ed8f30d9463df6dfb0920d67367.apk"
debug: Forwarding system:4724 to device:4724
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 forward tcp:4724 tcp:4724
debug: Pushing appium bootstrap to device...
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 push "E:\Tools\Appium\node_modules\appium\build\android_bootstrap\AppiumBootstrap.jar" /data/local/tmp/
debug: Pushing settings apk to device...
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 install "E:\Tools\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk"
debug: Pushing unlock helper app to device...
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 install "E:\Tools\Appium\node_modules\appium\build\unlock_apk\unlock_apk-debug.apk"
info: Starting App
debug: Attempting to kill all 'uiautomator' processes
debug: Getting all processes with 'uiautomator'
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "ps 'uiautomator'"
debug: No matching processes found
debug: Running bootstrap
debug: spawning: E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe -s emulator-5554 shell uiautomator runtest AppiumBootstrap.jar -c io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] io.appium.android.bootstrap.Bootstrap:
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 1
debug: [BOOTSTRAP] [debug] Socket opened on port 4724
debug: [BOOTSTRAP] [debug] Appium Socket Server Ready
debug: Waking up device if it's not alive
debug: Pushing command to appium work queue: ["wake",{}]
debug: [BOOTSTRAP] [debug] Loading json...
debug: [BOOTSTRAP] [debug] json loading complete.
debug: [BOOTSTRAP] [debug] Registered crash watchers.
debug: [BOOTSTRAP] [debug] Client connected
debug: [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"wake","params":{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: wake
debug: [BOOTSTRAP] [debug] Returning result: {"value":true,"status":0}
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "dumpsys window"
debug: Writing dumpsys output to E:\Tools\Appium\node_modules\appium.dumpsys.log
debug: Screen already unlocked, continuing.
debug: Pushing command to appium work queue: ["getDataDir",{}]
debug: [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"getDataDir","params":{}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: getDataDir
debug: dataDir set to: /data
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "am start -S -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -f 0x10200000 -n com.example.sampleclient
/com.example.sampleclient
.MainActivity"
debug: [BOOTSTRAP] [debug] Returning result: {"value":"/data","status":0}
debug: Waiting for pkg "com.example.sampleclient
" and activity "com.example.sampleclient
.MainActivity" to be focused
debug: Getting focused package and activity
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "dumpsys window windows"
debug: Device launched! Ready for commands
info: <-- POST /wd/hub/session 303 29083.151 ms - 9
debug: Setting command timeout to the default of 60 secs
debug: Appium session started with sessionId 3ae80c73-0c82-4c9e-81e8-628c270d0ad6
info: --> GET /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6 {}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6
debug: Request received with params: {}
info: <-- GET /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6 200 2.451 ms - 711 {"status":0,"value":{"platform":"WINDOWS","browserName":"","platformVersion":"4.1","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"warnings":{},"desired":{"platform":"WINDOWS","app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","browserName":"","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"},"app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"},"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: Responding to client with success: {"status":0,"value":{"platform":"WINDOWS","browserName":"","platformVersion":"4.1","webStorageEnabled":false,"takesScreenshot":true,"javascriptEnabled":true,"databaseEnabled":false,"warnings":{},"desired":{"platform":"WINDOWS","app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","browserName":"","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"},"app":"E:\Tools\SampleClient.apk","deviceName":"Default","platformName":"Android","app-package":"com.example.sampleclient
","device":"Android","app-activity":"MainActivity","version":"4.4.2"},"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: --> POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/timeouts/implicit_wait {"ms":80000}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/timeouts/implicit_wait
debug: Request received with params: {"ms":80000}
info: <-- POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/timeouts/implicit_wait 200 1.766 ms - 76 {"status":0,"value":null,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: Set Android implicit wait to 80000ms
debug: Responding to client with success: {"status":0,"value":null,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element
debug: Request received with params: {"using":"id","value":"com.example.sampleclient
:id/button_signin_execute"}
debug: Pushing command to appium work queue: ["find",{"strategy":"id","selector":"com.example.sampleclient
:id/button_signin_execute","context":"","multiple":false}]
info: --> POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element {"using":"id","value":"com.example.sampleclient
:id/button_signin_execute"}
debug: [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"find","params":{"strategy":"id","selector":"com.example.sampleclient
:id/button_signin_execute","context":"","multiple":false}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: find
debug: [BOOTSTRAP] [debug] Finding com.example.sampleclient
:id/button_signin_execute using ID with the contextId: multiple: false
debug: [BOOTSTRAP] [debug] Using: UiSelector[INSTANCE=0, RESOURCE_ID=com.example.sampleclient
:id/button_signin_execute]
debug: [BOOTSTRAP] [debug] Returning result: {"value":{"ELEMENT":"1"},"status":0}
debug: Responding to client with success: {"status":0,"value":{"ELEMENT":"1"},"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: <-- POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element 200 3787.398 ms - 87 {"status":0,"value":{"ELEMENT":"1"},"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: --> POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element/1/click {"id":"1"}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element/1/click
debug: Request received with params: {"id":"1"}
debug: Pushing command to appium work queue: ["element:click",{"elementId":"1"}]
debug: [BOOTSTRAP] [debug] Got data from client: {"cmd":"action","action":"element:click","params":{"elementId":"1"}}
debug: [BOOTSTRAP] [debug] Got command of type ACTION
debug: [BOOTSTRAP] [debug] Got command action: click
debug: [BOOTSTRAP] [debug] Returning result: {"value":true,"status":0}
info: <-- POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/element/1/click 200 3347.500 ms - 76 {"status":0,"value":true,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: Responding to client with success: {"status":0,"value":true,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: --> GET /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/contexts {}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/contexts
debug: Request received with params: {}
debug: Getting a list of available webviews
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "cat /proc/net/unix"
debug: WEBVIEW_1225 mapped to pid 1225
debug: Getting process name for webview
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "ps"
debug: Parsed pid: 1225 pkg: com.example
info: <-- GET /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/contexts 200 455.399 ms - 129 {"status":0,"value":["NATIVE_APP","WEBVIEW_com.example"],"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: from: u0_a77,1225,50,274880,58692,ffffffff,ac95940c,R,com.example
debug: returning process name: com.example
debug: Available contexts:
debug: ["WEBVIEW_com.example"]
debug: Available contexts: NATIVE_APP,WEBVIEW_com.example
debug: Responding to client with success: {"status":0,"value":["NATIVE_APP","WEBVIEW_com.example"],"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: --> POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/context {"name":"WEBVIEW_com.example"}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/context
debug: Request received with params: {"name":"WEBVIEW_com.example"}
debug: Getting a list of available webviews
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "cat /proc/net/unix"
debug: WEBVIEW_1225 mapped to pid 1225
debug: Getting process name for webview
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "ps"
debug: Parsed pid: 1225 pkg: com.example
debug: from: u0_a77,1225,50,274880,58692,ffffffff,b5a510c0,R,com.example
debug: returning process name: com.example
debug: Available contexts: NATIVE_APP,WEBVIEW_com.example
debug: ["WEBVIEW_com.example"]
debug: Available contexts: NATIVE_APP,WEBVIEW_com.example
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: E:\Tools\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
debug: [CHROMEDRIVER] Starting ChromeDriver (v2.10.289383) 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.example.sampleclient
","androidUseRunningApp":true,"androidDeviceSerial":"emulator-5554"}}}}
debug: Didn't get a new command in 60 secs, shutting down...
info: Shutting down appium session
debug: Removing app from device
debug: Uninstalling com.example.sampleclient

debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "am force-stop com.example.sampleclient
"
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 uninstall com.example.sampleclient

error: Chromedriver create session did not work. Status was 200 and body was {"sessionId":"a931983c4d83bd3fa9b9b6df5d5ae0ff","status":100,"value":{"message":"chrome not reachable\n (Driver info: chromedriver=2.10.289383,platform=Windows NT 6.1 SP1 x86_64)"}}
debug: Responding to client with error: {"status":13,"value":{"message":"An unknown server-side error occurred while processing the command. (Original error: Did not get session redirect from Chromedriver)","origValue":"Did not get session redirect from Chromedriver"},"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
info: <-- POST /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6/context 500 64788.964 ms - 280
info: --> DELETE /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6 {}
debug: Appium request initiated at /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6
info: Shutting down appium session
debug: Request received with params: {}
debug: Already in process of shutting down.
info: <-- DELETE /wd/hub/session/3ae80c73-0c82-4c9e-81e8-628c270d0ad6 200 0.840 ms - 76 {"status":0,"value":null,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: Cleaning up appium session
debug: Responding to client with success: {"status":0,"value":null,"sessionId":"3ae80c73-0c82-4c9e-81e8-628c270d0ad6"}
debug: App was uninstalled
debug: Pressing the HOME button
debug: executing: "E:\Tools\adt-bundle-windows-x86_64-20140702\sdk\platform-tools\adb.exe" -s emulator-5554 shell "input keyevent 3"
debug: Stopping logcat capture
debug: Logcat terminated with code null, signal SIGTERM
debug: Cleaning up Chromedriver
debug: Killing chromedriver
debug: Chromedriver exited with code null
debug: (killed by signal SIGTERM)
debug: [BOOTSTRAP] [debug] Got data from client: {"cmd":"shutdown"}
debug: [BOOTSTRAP] [debug] Got command of type SHUTDOWN
debug: [BOOTSTRAP] [debug] Returning result: {"value":"OK, shutting down","status":0}
debug: Sent shutdown command, waiting for UiAutomator to stop...
debug: [BOOTSTRAP] [debug] Closed client connection
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: numtests=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=.
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: id=UiAutomatorTestRunner
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: test=testRunServer
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: class=io.appium.android.bootstrap.Bootstrap
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: current=1
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: 0
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS: stream=
debug: [UIAUTOMATOR STDOUT] Test results for WatcherResultPrinter=.
debug: [UIAUTOMATOR STDOUT] Time: 106.116
debug: [UIAUTOMATOR STDOUT] OK (1 test)
debug: [UIAUTOMATOR STDOUT] INSTRUMENTATION_STATUS_CODE: -1
debug: UiAutomator shut down normally
debug: Cleaning up android objects
debug: Cleaning up appium session
debug: We shut down because no new commands came in
@nolanlawson
Copy link

Same here. After switching to the webview context, I try to select elements, and it just times out after 60 seconds with no response. Android 4.4 Motorola device, Chromedriver 2.11, Appium 1.2.4, OS X Mavericks.

I can do everything except switch to the webview and start selecting elements after that. My code:

.contexts()
    .then(function (ctxs) {
      console.log(ctxs);
      var newContext = ctxs.filter(function (ctx) {
         return /WEBVIEW/.test(ctx);
      })[0];
      return driver.context(newContext);
    })
    .elementById('someId')

And the last logs are:

info: [debug] Making http request with opts: {"url":"http://127.0.0.1:9515/wd/hub/session/82a241fc903672be31af769edfc06e5b/element","method":"POST","json":{"using":"id","value":"someId"}}
info: [debug] Didn't get a new command in 60 secs, shutting down...

@triager triager added the Needs Triage bugs which are not yet confirmed label Oct 30, 2014
@imurchie
Copy link
Contributor

imurchie commented Dec 2, 2014

These are two different issues. Do they still occur? And if they do, does ChromeDriver by itself work?

@imurchie imurchie closed this as completed Jan 6, 2015
@jlipps jlipps removed the Needs Triage bugs which are not yet confirmed label Apr 22, 2015
@lock
Copy link

lock bot commented May 1, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators May 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@imurchie imurchie

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@nolanlawson @jlipps @himanshushekhar @imurchie @triager