IOS: Some element are not visible through Appium Inspector


I am automating a hybrid app in IOS, not able to identify identify an element inside UIACollectionCell (Inside CollectionCell there are many element,some are visible and some not).

This is the tree

one more button is missing…

Need reason whether it is issue with Appium or development.
And suggest me some solution to overcome it…


I can’t think of a reason why Appium would prohibit any visibility inside of a UIACollecitonCell.
You can verify for certain whether or not this is a limitation to your App under Test (AUT) or to Appium by trying one of these 2 options:

  1. Reveal. If you have access to the AUT source, you can use reveal without having to modify the AUT source by following the directions here:

  2. Apple also ships with an accessibility inspector. If you have a simulator build, it’s easier. Just follow the directions here:

Hope this helps!

Hi Eric,

Thanks for your responce.
Actually i don’t have a Xcode project, all i have is .ipa file.
The sugessions you gave need Xcode project

Is there any other go…please suggest


Right on.
Your best bet then is to use voiceover. That should speak out the UIAccessibilityLabels as you navigate to them in your app

I have a similar problem, only in my app it is a custom keyboard that the Appium Inspector cannot see. Sometimes it can see the alphanumeric keypad which is a displayable option of the custom keypad, but other times it can’t.

I also have the opposite problem. In a very large table view, iOS doesn’t really create all the underlying cells until you start scrolling. It actually only keeps a few cells in memory (the visible ones plus a few “boundary” cells) at any given time and puts new data into the existing cells as you scroll. Somehow Appium can see the hundreds of “invisible” cells in the table, but when I try to tell it to scroll to one of these it always fails.

Any tips on either of these visibility/interaction issues would be greatly appreciated!

Hi Eric,
Even voiceover is help less…
once i touched element it doesn’t get highlighted.

Any other options…ideas are welome :grin:


Sorry not offhand. I would try my best to get the source or use the appium tools of arc and the inspector. Maybe there are others who can add?


Hi Eric,

On discuss with development team,They say’s "The icon is composed by 3 different elements.

1.- There is a wrapper that belongs to the Border View class.

2.- Inside this wrapper, there is a UIButton.

3.- Also there is a CloudView inside this wrapper."

according to this icon should be a UIButton but not shown in inspector…

Is this Appium Issue??


I got Storyboard_xml is that useful for something???

Here’s what I did.
If you use the
You can download the iOS source code, build this yourself and do some learning :slightly_smiling:

I did this and I stubbed out the following:
An example of the appium inspector showing one button with a label and one without.
An example of reveal program comparing the same buttons.
An example of what the Storyboard in the source looks like comparing the same buttons

What I noticed:

  1. Reveal and Appium seem to report the same results - that’s good.
  2. It seems like if your app has a button icon without text and an accessibility label, hint, or identifier is not explicitly set - then the label does not show up upon interrogation. I’ll bet that’s what is happening wth you.


  1. I would encourage you to look at the Storyboard.xml that you have and see if that matches up with what I am saying.
  2. I would encourage your developers to look at [Apple’s Accessibility Guidelines] ( Most likely they need to add an accessibility element either in the storyboard or programmatically.

@CMTaylor. You are correct. While you cannot scroll to the table cells ofscreen, you should be able to click on them. Do you need to scroll to them first? Otherwise I would just directly click. If you need to actually scroll to them first, I would do the TouchAction commands to swipe down page by page and check for your element each time. It’s not ideal, but it works :slightly_smiling:

Hope it’s helpful. Let me know if further questions.

Thanks @shermaneric it really helped a lot :innocent:

our developer had not included the accessibility thing to icon that’s the problem here :blush:

1 Like

Could you please provide code snippet for scroll down page by page.

Hi mani: for iOS or android?

Honestly, I haven’t had the need to scroll on iOS as ui automation can “select” table rows offscreen and click them without the need to scroll.

I know there are scroll_to and scroll_to_exact methods in ruby. They previously had problems but if you search this board I believe things are better. I haven’t tried it out though.

In android I simply rely on touch actions with sadly the plain logic of "swipe down, check to see if my element is there…if not continue. There’s some logic for checking that I’m at the bottom of the screen by comparing the contents of the last table row on each iteration. Not ideal but it works.

More is here. I would try the scroo_to methods first though

Surely this depends on how the memory management comes in to play? , you can’t click on a cell that hasn’t been allocated yet, if your using dynamic tables & cell reusability.

+1 for Reveal, it’s a really good tool to debug accessibility / views in general.

I would trial the application and make adhoc changes to accessibility and see if the changes take affect correctly, if they do make similar changes to the project to reflect the accessibility hierarchy thats needed.

If you can share any snippet’s of code that replicate the issue I’m sure we will be able to assist, just pop it on a gist or repo :smile:

Hi. My problem is that with iPhone5 I see all the elements of my app, with iPhone7 only some of them (like the first two layers).

Hi, I have a similar issue with dropdown list, not able to inspect those list of items on iOS native app. My dev has added the accessibility identifier to the list and the code is
func makeUIView(context: Context) -> UITextField {

let stateTextField = AutoCompletionTextField()
stateTextField.accessibilityIdentifier = “stateTextField”
stateTextField.autocompleteTableView?.accessibilityIdentifier = “stateAutoCompleteTableView”
return stateTextField

Appium Inspector (2022.5.4) is displaying the locator “stateTextField”, not “stateAutoCompleteTableView” for the dropdown list. Can you please suggest me, what could be the reason for the locator not displaying in App Source.