Hi all,
I’m looking for support to test a hybrid app on real android phone.I have followed the appium documentation but still only getting the native_app context.
my operation scenario as follows:
1、setWebContentsDebuggingEnabled：true
2、real android phone and version 4.4.2
3、use selendroid
4、go into the webview and can be show the webview by chrome dev tool.
5、use appium v1.3.4 and java-client-2.1.0.jar
But only show the native_app context when i call driver.getContextHandles().
Anyone who had the same problem and could tell me why?
Thank you for giving me provide ideas to solve the problem.
the log as follow:
info: [debug] WEBVIEW_19249 mapped to pid 19249
info: [debug] Getting process name for webview
info: [debug] executing cmd: D:\Android\sdk\platform-tools\adb.exe -s HC47VWW06348 shell “ps”
info: [debug] Parsed pid: 19249 pkg: com.xxxxx.xxxxxxx:web
info: [debug] from: u0_a79,19249,358,752576,82328,ffffffff,00000000,R,com.xxxxx.xxxxxxx:web
info: [debug] returning process name: com.xxxxx.xxxxxxx:web
info: [debug] Available contexts: undefined
info: [debug] [“WEBVIEW_com.xxxxx.xxxxxxx:web”]
info: [debug] Making http request with opts: {“url”:“http://localhost:8080/wd/hub/session/d35aa4dc-5eae-9b2f-2507-d91952be2854/window_handles",“method”:"GET”}
info: [debug] Available contexts: [“NATIVE_APP”]
info: [debug] Responding to client with success: {“status”:0,“value”:[“NATIVE_APP”],“sessionId”:“d35aa4dc-5eae-9b2f-2507-d91952be2854”}
info: ← GET /wd/hubssion/d35aa4dc-5eae-9b2f-2507-d91952be2854/contexts 200 120679.175 ms - 86 {“status”:0,“value”:[“NATIVE_APP”],“sessionId”:“d35aa4dc-5eae-9b2f-2507-d91952be2854”}
info: → DELETE /wd/hubssion/d35aa4dc-5eae-9b2f-2507-d91952be2854 {}
info: Shutting down appium session
info: [debug] Stopping selendroid server
@Simon_
Thanks a lot for your reply!
I use selenroid and had the problem above.
But it also had other error as follow when i used appium and replaced the chromedirve with 2.14 .
I have tried in
-Android v4.4.2
-HTC device
-Appium version 1.3.4
-chromedriver version 2.1.4
-chrome version 40.0.2214.89
the server logs:
info: [debug] Available contexts: NATIVE_APP,WEBVIEW_com.xxxxx.yyyyy:web
info: [debug] [“WEBVIEW_com.xxxxx.yyyyy:web”]
info: [debug] Available contexts: NATIVE_APP,WEBVIEW_com.xxxxx.yyyyy:web
info: [debug] Connecting to chrome-backed webview
info: [debug] Creating Chrome session
info: [debug] Set chromedriver binary as: D:\appium\AppiumForWindows\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: D:\appium\AppiumForWindows\Appium\node_modules\appium\build\chromedriver\windows\chromedriver.exe
info: [debug] [CHROMEDRIVER] Starting ChromeDriver 2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf) 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.xxxxx.yyyyy”,“androidUseRunningApp”:true,“androidDeviceSerial”:"HC47VWW06348”}}}}
error: Chromedriver create session did not work. Status was 200 and body was {“sessionId”:“3dfd06350740afefdeb6792783bcfec5”,“status”:100,“value”:{“message”:“chrome not reachable\n (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Windows NT 6.1 SP1 x86_64)”}}
info: [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”:“a88f3898-7314-42d9-96b3-4c495655dcd8”}