Re: Android: MobileWeb: Not able to get it work!!

[Ram Rai]

Hi Ritika,

As u have mentioned that, "I have done a lot on native app's for both iPhone and Android" and from the last one week Im really struggling about testing my apps using appium....

I have succeeded only on the sample app provided along with the tutorial on the website...

Please let me know that how to test my own android n iphone apps using appium??

Thnx in advance....

On Friday, August 9, 2013 6:57:56 PM UTC+5:30, ritika mishra wrote:

Hi all,

I have done a lot on native app's for both iPhone and Android but am new to MobileWeb. I just tried my hands on it today and got the following error:

info: Welcome to Appium v0.8.0 (REV 0c1eba53f255cd322fe854aae9dcf4e179e97f85)

info: Appium REST http interface listener started on 10.101.23.155:4723

info: socket.io started

info: Looks like we want chrome on android, setting pkg/activity

debug: Appium request initiated at /wd/hub/session

info: Creating new appium session f24aeb39-232c-406f-bd43-3d4a190a17fd

debug: Request received with params: {"desiredCapabilities":{"platform":"MAC","app":"chrome","Device":"Android","browserName":"Android","version":"4.1.2"}}

info: Ensuring Chromedriver exists

info: Spawning chromedriver with: /usr/bin/chromedriver

info: [CHROMEDRIVER] Starting ChromeDriver (v2.2) on port 9515

info: [CHROMEDRIVER STDERR] objc[2450]: Object 0x127ea70 of class NSThread autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug

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: Chromedriver create session did not work. Status was 200 and body was [object Object]

info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: Did not get session redirect from Chromedriver)","origValue":"Did not get session redirect from Chromedriver"},"sessionId":"f24aeb39-232c-406f-bd43-3d4a190a17fd"}

error: Failed to start an Appium session, err was: Error: Did not get session redirect from Chromedriver

POST /wd/hub/session 500 543ms - 285

info: Clearing out appium devices

Here i am not even able to understand the problem. Is is due to chrome, or appium or my code!!!

Thanks,

Ritika

[ritika mishra]

[Aniket Gadre]

I just read Jonathan mentioning in one of the previous threads that there is an issue with latest update of ChromeDriver v2.2.

--
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.
 
 

--
Best Regards,
Aniket Gadre
Test Automation Lead
Amdocs , Pune.
E-add: aniket...@amdocs.com

[Jonathan Lipps]

That error is coming from Chromedriver. What version are you using?

[riti mish]

Hi Jonathan,

I was using ChromeDriver version 2.2. I saw, an issues had been reported at "https://github.com/appium/appium/issues/969" for ChromeDriver 2.2, but it was in "closed" state (i assume it has been fixed), so i tried again and it still did not work. In one of your thread you had mentioned that ChromeDriver was working fine with version 2.0, so i removed version 2.2 and installed 2.0. It still did not work for me, I am pasting the log from version 2.0.

Note: I am using the latest version of appium (8.3.1)

Thanks, 

Ritika

Appium Log:

info: Welcome to Appium v0.8.3 (REV 8b947cf9f5a8772553af12b8096d77b2ac7fd2af)

info: Appium REST http interface listener started on 10.101.23.155:4723

info: socket.io started

debug: Appium request initiated at /wd/hub/session

info: Looks like we want chrome on android

debug: Request received with params: {"desiredCapabilities":{"platform":"MAC","app":"chrome","Device":"Android","browserName":"Android","version":"4.1.2"}}

info: Clearing out any previous sessions

info: Creating new appium session 68a58493-ba3f-49c6-9cdb-6cee252b8bf0

info: Ensuring Chromedriver exists

info: Spawning chromedriver with: /usr/bin/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\"}}}"}

info: [CHROMEDRIVER STDERR] [0.743][INFO]: received WebDriver request: POST /wd/hub/session {

   "desiredCapabilities": {

      "chromeOptions": {

         "androidPackage": "com.android.chrome"

      }

   },

   "sessionId": null

}

error: Chromedriver create session did not work. Status was 200 and body was {"sessionId":"","status":13,"value":{"message":"unknown error: Adb command \"host:devices\" failed, is the Adb server running?\n  (Driver info: chromedriver=2.0,platform=Mac OS X 10.7.5 x86_64)"}}

info: [CHROMEDRIVER STDERR] [0.764][INFO]: sending WebDriver response: 200 {

   "sessionId": "",

   "status": 13,

   "value": {

      "message": "unknown error: Adb command \"host:devices\" failed, is the Adb server running?\n  (Driver info: chromedriver=2.0,platform=Mac OS X 10.7.5 x86_64)"

   }

}

info: Responding to client with error: {"status":6,"value":{"message":"A session is either terminated or not started (Original error: Did not get session redirect from Chromedriver)","origValue":"Did not get session redirect from Chromedriver"},"sessionId":"68a58493-ba3f-49c6-9cdb-6cee252b8bf0"}

POST /wd/hub/session 500 813ms - 285

info: Clearing out appium devices

info: Clearing out any previous sessions

error: Failed to start an Appium session, err was: Error: Did not get session redirect from Chromedriver

[Jonathan Lipps]

That looks like Chromedriver can't find the device online. If you run adb kill-server && adb-devices, does that help?

[Pradeepta Swain]

I am facing the same problem. ChromeDriver ver - 2.2 . I tried running adb kill-server && adb-devices, but no success

Thanks,
Pradeepta

[Aniket Gadre]

Please do not hack the threads, start the new ones for new issues.

--

[Pradeepta Swain]

Any updates on chromedriver not working on Android?

Thanks,

Pradeepta

On Monday, 12 August 2013 11:04:14 UTC+5:30, Jonathan Lipps wrote:

[hari haran]

Could you please provide any updates on chrome driver working on Android?

[Pradeepta Kumar Swain]

Chromedriver is working fine, except for few mobile gestures ( Swipe, Flick .. ) . Can you please post your error log from Appium console?

Thanks,
Pradeepta

You received this message because you are subscribed to a topic in the Google Groups "Appium-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/appium-discuss/GKec-_dCp-4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to appium-discus...@googlegroups.com.

[hari haran]

 

Please find error logs

 

info: Welcome to Appium v0.13.0
info: Appium REST http interface listener started on 127.0.0.1:4723
   info  - socket.io started

debug: Appium request initiated at /wd/hub/session

debug: Request received with params: {"desiredCapabilities":{"platform":"WINDOWS
","app":"chrome","browserName":"","device":"Droid","version":"4.2"}}

info: Looks like we want chrome on android

info: Creating new appium session 16bbead5-6ed5-47ed-86d8-2aa444cd5a53
info: Ensuring Chromedriver exists
info: Spawning chromedriver with: C:\AppiumDownloads\chromedriver.exe

info: [CHROMEDRIVER] Starting ChromeDriver (v2.2) on port 9515

info: Creating Chrome session
info: Making http request with opts: {"url":"http://127.0.0.1:9515/wd/hub/sessio

n","method":"POST","json":{"sessionId":null,"desiredCapabilities":{"chromeOption
s":{"androidPackage":"com.android.chrome"}}}}
error: Chromedriver create session did not work. Status was 200 and body was {"s
essionId":"ee3eefd3b69009ae7f96fbcaabd2d82a","status":100,"value":{"message":"ch
rome not reachable\n  (Driver info: chromedriver=2.2,platform=Windows NT 6.1 SP1
 x86_64)"}}
info: Cleaning up appium session

error: Failed to start an Appium session, err was: Error: Did not get session re
direct from Chromedriver

info: Responding to client with error: {"status":33,"value":{"message":"A new se
ssion could not be created. (Original error: Did not get session redirect from C

hromedriver)","origValue":"Did not get session redirect from Chromedriver"},"ses

sionId":null}
POST /wd/hub/session 500 28932ms - 242b

[Pradeepta Kumar Swain]

Is your device rooted ?

[Jonathan Lipps]

This error is fixed in master; please wait for the next release