Error in using UIAutomatorviewer for testing Android app in Appium

Question

I have to automate an Android application, I am doing the same through Appium.

The problem I am facing is after launching the Appium server, the app is getting installed in the emulator 4.4.2. To inspect the element I am using UIAutomatorviewer which comes default with SDK. But while inspecting the element of the app, I am getting the error:

Error obtaining UI hierarchy
Reason:Error while obtaining UI hierarchy XML file.com.android.ddmlb.SynchException.Remote object doesn't exist.

I tried to find the solution so that I can inspect the element so that I can script, but in vain.

Can someone please tell how to fix the issue so that I can inspect elements?
Is there any other way I can inspect element in the app apart from using UIAutomator viewer?

score 31 · Answer 1 · answered Aug 11 '14 at 12:56

31

After my tryst with the uiautomator viewer i came to know that we get the error only when:

appium server is running and we try to capture the screenshot using uiautomatorviewer.

So, whenever you want to use uiautomatorviewer make sure that server is in stopped state.

answered Aug 11 '14 at 12:56

Rancho

976
1
8
16

This is definitely the most common reason. A quick command-line way to kill appium servers is `taskkill /F /IM node.exe` (warning: will kill all node servers). However, for the case where no Appium server was running, the answer below worked better for me: http://stackoverflow.com/a/28526871/682912 – Vish Nov 18 '15 at 04:25
4

It didnt helped in my case, I have stopped the Appium server though – AnswerDroid Jan 05 '16 at 09:20

score 12 · Answer 2 · edited Jul 05 '17 at 13:15

12

I fixed the same issue by using following methods.

(1) Connect your Android device to your development machines;

(2) Go to command line in terminal or DOS command line for Windows;

(3) Using "adb shell" into your Android devices;

(4) Change the user to root by input "su root" in command line;

(5) Change the access right to /data/local/tmp by input "chmod 777 /data/local/tmp";

(6) Go back to uiautomatorviewer and do screen shot again, the error should be gone;

I guess there are some file can't be access if it doesn't own right in /data/local/tmp.

edited Jul 05 '17 at 13:15

conradkleinespel

6,560
10
51
87

answered Feb 15 '15 at 14:03

Damon Song

374
2
4

1

when I tried to follow it I just got "/system/bin/sh: su: inaccessible or not found" after step 4 – Adam Burley May 03 '20 at 13:23

score 10 · Answer 3 · edited May 18 '16 at 03:23

10

Make sure everything on your screen is static. And flashing input cursor is also not allowed. Any painting actions will stop uiautomator from dumping current UI.

You can test by using following adb command:

adb shell uiautomator dump /data/local/tmp/uidump.xml

if the message ERROR: could not get idle state. appears, you are suffering from this issue.

See lines 87 & 101 of DumpCommand:

try {
  ...   
  uiAutomation.waitForIdle(1000, 1000 * 10);
  ...
} catch (TimeoutException re) {
  System.err.println("ERROR: could not get idle state.");
  return;
}

edited May 18 '16 at 03:23

dimo414

47,227
18
148
244

answered May 18 '16 at 02:41

Shawn.G

101
1
4

Yep, I was getting the same error. And I observed that timer is running on particular screen. When I stopped the timer. It work like a charm. – Amit Yadav Nov 29 '16 at 06:41
I got that idle state error but not sure how to resolve it because I don't have access to the source code of the app under test so I can't disable timers etc. – Adam Burley May 03 '20 at 13:28

score 7 · Answer 4 · answered Feb 16 '15 at 12:20

7

Easiest solution..

Restart the device. Restart uiautomatorviewer.

Worked like a charm for me .... :P

answered Feb 16 '15 at 12:20

Rohit Rokde

622
2
8
16

score 4 · Answer 5 · answered Jul 13 '16 at 12:34

4

Stop the Appium Server. Then try again. It works.

answered Jul 13 '16 at 12:34

Santosh Pillai

8,169
1
31
27

score 1 · Answer 6 · answered Aug 11 '15 at 07:21

1

I had the same problem because I used "adbd insecure". So I just disabled "adbd insecure", and reload uiautomatorviewer, everything is OK.

answered Aug 11 '15 at 07:21

na zeng

11
1

score 1 · Answer 7 · answered Apr 15 '16 at 09:03

1

In case of rooted devices: Enable the root access in developer options for adb. Restart adb as root

answered Apr 15 '16 at 09:03

user1302884

783
1
8
16

score 1 · Answer 8 · edited Mar 12 '17 at 19:54

1

Answer to your question #2 You can inspect Android app directly from your real Android device.

You need to:

Connect Android device to your computer/laptop
Go to Android device Settings -> Enable Developer Options and Android debbuging

Please see here:

Start the app you wish to inspect in your Android device
Open up the Chrome browser on your computer/laptop and do a right click -> More Tools -> Inspect devices -> Click on your device -> (Click on Android device OK to authorize) -> Click Inspect

Please see here:

That's it. Hope it helps!

edited Mar 12 '17 at 19:54

TWiStErRob

44,762
26
170
254

answered Jun 29 '16 at 06:43

Stipe

480
5
18

Is this perhaps CyanogenMod specific? Or root required? Doesn't seem to work for me. – Richard Le Mesurier Jul 06 '17 at 11:38

score 1 · Answer 9 · answered Sep 12 '16 at 06:02

I have spent over a week to resolve this issue. When you connect your device and using ASM 3.0, when screen is projected open the UIAutomator to capture the current android screen. Without Appium it should capture. For use Android Studio instead of android sdk. Uninstall and reinstall Android Studio. It is working perfect for me now.

score 1 · Answer 10 · answered Jun 07 '17 at 17:09

1

I got also the same issue (Also if Appium Server was not running). After switch, OFF / ON USB-Debugging was working for me.

answered Jun 07 '17 at 17:09

Kumar

11
1

score 1 · Answer 11 · answered Nov 15 '17 at 05:48

1

I got it resolved

I closed the Appium Server running on my machine and opened it again. Later open uiautomater, and it worked for me

answered Nov 15 '17 at 05:48

Piyush Jeswani

29
2

score 1 · Answer 12 · answered Aug 04 '18 at 06:08

1

The one that works is in this path:

Android/Sdk/tools/bin/uiautomatorviewer

Paste this in your terminal and it will run automator that works

answered Aug 04 '18 at 06:08

Sajid Zeb

1,806
18
32

score 0 · Answer 13 · answered Jun 28 '16 at 10:10

0

we have to use device which has API level morethan 17 or jelly bean

answered Jun 28 '16 at 10:10

Pawan Rajen

19
1

score 0 · Answer 14 · edited Feb 13 '17 at 15:17

Way to bypass the ERROR:

could not get idle state.

By using uiautomator to get uix and screenshot.

public class DeviceMethods extends UiAutomatorTestCase {
public void dump(){


    try {
        getUiDevice().dumpWindowHierarchy("window_dump.uix") ;
        getUiDevice().takeScreenshot(new File("/data/local/tmp/window_dump.png"));


    } catch (Exception e) {

    }

}

you need to create the uiautomator jar and push it to /data/local/tmp

use this tutorial on how to use uiautomator

after you get the files just open them in uiautomatorviewer

score 0 · Answer 15 · answered Jul 11 '17 at 19:18

What worked for me:

stop appium
open an emulator device (tested with Android 7.1.1)
go into settings > developer options > Enable view attribute inspection
open a shell on the computer, cmd or terminal depending on your OS
enter the following commands:
adb shell
su
cd /data
cd /local
chmod 777 tmp

start uiautomatorviewer
take an xml screenshot

"su chmod 777 /data/local/tmp" didnt work for me so I drilled down and it worked.
I assume that you have to do this in an emulator and not a physical device unless the device is rooted. ¯ \ _ (ツ)_/¯

Lotsa Luck!

score 0 · Answer 16 · answered Jan 31 '18 at 15:38

0

This happens because adb is using port and it's blocked by appium server.

I have found out best solution for this

Kill the adb.exe from taskbar processes and try launching uiautomatorviewer again

answered Jan 31 '18 at 15:38

Praveen Chauhan

1

score 0 · Answer 17 · answered May 08 '18 at 03:35

0

Check whether you have enabled these under "developer options" in the phone.

Verify apps via USB
View attribute inspection
USB debugging

answered May 08 '18 at 03:35

Kumudu S. Liyanage.

1
2

score 0 · Answer 18 · answered Jul 19 '18 at 09:50

1) stop appium Server

2) open an emulator device

3) go into settings > developer options > Enable view attribute inspection

4) developer options in invisible? Go into settings > Tap on About device/phone > Scroll down till the last option(Build number) > Continuously Tap on "Build number" for 7 times > you should get an Toast message "You're a developer" > come back from that screen > Go back into settings > Now you should see developer options Tap on it > Enable view attribute inspection

5) You should no more get this error message

score 0 · Answer 19 · answered Jun 06 '22 at 07:02

0

Why don't you use appium inspector instead? You can download it and follow instructions from here

answered Jun 06 '22 at 07:02

S.Hasan

354
2
14

score -1 · Answer 20 · answered Oct 05 '18 at 15:43

-1

try switching Off and then ON the USB debugging option.. this work for me

answered Oct 05 '18 at 15:43

AutoGeek

11

Error in using UIAutomatorviewer for testing Android app in Appium

20 Answers20

Linked