WaitForScreen fails 0.4.0.pre10

[bootstraponline]

Step unsuccessful: Screen A not found. Current activity is B
(RuntimeError)

I looked at the screenshot and it's on A, however getCurrentActivity
reports screen B. It appears this is a known issue with robotium. Is
there anything that can be done to WaitForScreen so it works properly?

http://code.google.com/p/robotium/issues/detail?id=179

[Jonas Maturana Larsen]

We could use adb for that.

I think something like this would work:

adb shell dumpsys window windows | grep -E 'mFocusedApp'

(Grep would have to be done in a Windows friendly way)

I guess this could also be used to check if the expected external app is started when you expect that - haven't really though it through :)

- Jonas

[bootstrap online]

I implemented this.
https://gist.github.com/4589830

[bootstrap online]

I used your "focused_activity" code to define a new
"wait_for_activity" method which always detects the correct activity.
It'd be nice to have something similar in the official repository.

[Jonas Maturana Larsen]

It will get there. I promise! :)

Maybe it should be named "current_activity" instead because "focused" doesn't make much sense.

- Jonas

[bootstrap online]

I agree that makes more sense.

On Tue, Jan 22, 2013 at 4:57 PM, Jonas Maturana Larsen