Chromedriver with appium behaving weird. Please read the whole post.
Adil Imroz
info: Welcome to Appium v0.8.2 (REV e9cc66197ad6a3496322bd77a8699509fc761b69)
info: Appium REST http interface listener started on 0.0.0.0:4723
info: socket.io started
info: Looks like we want chrome on android
debug: Appium request initiated at /wd/hub/session
info: Clearing out any previous sessions
info: Creating new appium session 29f51ec7-dae4-46c7-9057-1cb55f730f25
info: Ensuring Chromedriver exists
debug: Request received with params: {"desiredCapabilities":{"app":"Chrome","device":"Android"}}
info: Spawning chromedriver with: /Users/Adil/Documents/chromedriver
info: Creating Chrome session
info: Making http request with opts: {"url":"http://127.0.0.1:9515/wd/hub/session","method":"POST","jar":false,"headers":{"Content-Length":98,"Content-Type":"application/json;charset=UTF-8","Host":"127.0.0.1:9515"},"body":"{\"sessionId\":null,\"desiredCapabilities\":{\"chromeOptions\":{\"androidPackage\":\"com.android.chrome\"}}}"}
error: Failed to start an Appium session, err was: Error: connect ECONNREFUSED
info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: connect ECONNREFUSED)","code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect","origValue":"connect ECONNREFUSED"},"sessionId":"29f51ec7-dae4-46c7-9057-1cb55f730f25"}
POST /wd/hub/session 500 1579ms - 316
info: Clearing out appium devices
info: Clearing out any previous sessions
info: [CHROMEDRIVER] Starting ChromeDriver (v2.6.232908) on port 9515
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Now when I restart appium and run the test I get this second type of error
LOG 2
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
info: Welcome to Appium v0.8.2 (REV e9cc66197ad6a3496322bd77a8699509fc761b69)
info: Appium REST http interface listener started on 0.0.0.0:4723
info: socket.io started
info: Looks like we want chrome on android
debug: Appium request initiated at /wd/hub/session
info: Clearing out any previous sessions
info: Creating new appium session 6928ba14-31be-48ad-a1f8-b011520a2c3e
info: Ensuring Chromedriver exists
debug: Request received with params: {"desiredCapabilities":{"app":"Chrome","device":"Android"}}
info: Spawning chromedriver with: /Users/Adil/Documents/chromedriver
info: [CHROMEDRIVER] Starting ChromeDriver (v2.6.232908) on port 9515
info: [CHROMEDRIVER STDERR] [0.004][SEVERE]: Could not bind socket to 0.0.0.0:9515
info: [CHROMEDRIVER] Port not available. Exiting...
error: Failed to start an Appium session, err was: Error: Chromedriver quit before it was available
info: Chromedriver exited with code 1
info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: Chromedriver quit before it was available)","origValue":"Chromedriver quit before it was available"},"sessionId":"6928ba14-31be-48ad-a1f8-b011520a2c3e"}
POST /wd/hub/session 500 375ms - 275
info: Clearing out appium devices
info: Clearing out any previous sessions
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Regards
Adil Imroz
Jonathan Lipps
--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
Aniket Gadre
Tejesh G
We are trying to perform mobile browser automation on ANDROID EMULATOR(Device-Nexus One) on Windows 7 Environment.
We have been reading in blogs that APPIUM Version 0.11.3 supports CHROME.
As per the blog information we have installed CHROME.apk Version 30(Chrome_30.0.1599.92.apk)
We have specified the chromedriver.exe path in PATH variable.
The blog says that there is no need of specifying the "app-package" and "app-activity" when we try to launch a browser.
In spite of following the steps specified in blogs we are facing issues in running tests through APPIUM.
I get the following error when I try to execute the test:
","app":"chrome","device":"Android","version":"4.2"}}
info: Looks like we want chrome on android
info: Ensuring Chromedriver exists
info: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Could not find chromed
river, is it on PATH?
info: Responding to client with error: {"status":33,"value":{"message":"A new se
ssion could not be created. (Original error: Could not find chromedriver, is it
on PATH?)","origValue":"Could not find chromedriver, is it on PATH?"},"sessionId
":null}
POST /wd/hub/session 500 195ms - 236b
Would be great if any one can help in resolving the issue.
Regards
Tejesh
Aniket Gadre
--
http://appium.io
---
You received this message because you are subscribed to the Google Groups "Appium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to appium-discus...@googlegroups.com.
Visit this group at http://groups.google.com/group/appium-discuss.
For more options, visit https://groups.google.com/groups/opt_out.
Tejesh G
Tejesh G
I did restart IDE after adding chrome driver path to the PATH variable. But still facing the same issue.
