UiAutomator issue is giving runtime error while exceuting scripts in Androidviewclient #84

Closed
DivyaSharma17 opened this Issue Jun 30, 2014 · 1 comment

Comments

Projects
None yet
2 participants

I am trying to automate the UI of android.For Automating I using AndroidViewClient version 5.1.1, Android API level 18 and devices (Nexus 4 and Nexus 7). I am using Ubuntu 12.10. Earlier after every view i was giving a sleep of 1 or 2 secs, due which my scripts were working fine, but it was taking longer time. Now i have removed all the sleeps, but while executing the same scripts, I am getting UiAutomator runtime issue.

raise RuntimeError ( '''ERROR: UiAutomator output contains no valid information. UiAutomator was killed, no reason given.''')

There is no specific step to re-produce this runtime error. Can you plz help me by solving this problem.

Owner

dtmilano commented Jun 30, 2014

It takes some time for UIAutomator to generate the dump and I don't think
it could be called concurrently, so if you invoke it too soon before the
previous one finished you'll encounter this problem.

On Mon, Jun 30, 2014 at 12:43 PM, DivyaSharma17 notifications@github.com
wrote:

I am trying to automate the UI of android.For Automating I using
AndroidViewClient version 5.1.1, Android API level 18 and devices (Nexus 4
and Nexus 7). I am using Ubuntu 12.10. Earlier after every view i was
giving a sleep of 1 or 2 secs, due which my scripts were working fine, but
it was taking longer time. Now i have removed all the sleeps, but while
executing the same scripts, I am getting UiAutomator runtime issue.

raise RuntimeError ( '''ERROR: UiAutomator output contains no valid
information. UiAutomator was killed, no reason given.''')

There is no specific step to re-produce this runtime error. Can you plz
help me by solving this problem.


Reply to this email directly or view it on GitHub
#84.

Have you read my blog ?
http://dtmilano.blogspot.com
android junit tests ui linux cult thin clients

@dtmilano dtmilano closed this Sep 19, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment