Unable to find element for IOS app for particular screen


#1

Hi,

I am using IOS app for automating through appium. In some screens I am unable to find any elements present in that particular screen. As discussed with developer, they have added accessibility ID in all the elements. Still when I am trying to inspect that particular screens no hierarchy and tags are present. Also we have tried to search the elements through script using accessibility id, still unable to identify the objects. Could you please suggest what more work around will be helpful.

Thanks
Bhagyashree


#2

@Bhagyashree_Panigrah first share:

  1. result of ‘driver.getPageSource()’ on needed screen (pls NOT in forum but outside link e.g. to https://gist.github.com/)
  2. image of screen

#3

![34%20PM|690x431]

Please find the screenshot of the appium inspector view while spying on the particular screen.


#4

@Bhagyashree_Panigrah it is not result of “result of ‘driver.getPageSource()’”. AppiumGUI can be wrong.

Also does your app NATIVE? or maybe Web wrapped?


#5

@Bhagyashree_Panigrah Which version of Appium you are using?


#6

Appium version - 1.10.0


#7

OK then it should work. Previous versions of appium was having issues with inspecting Hybrid app but in latest appium it works fine. Is your app is native or Hybrid?


#8

Hi Aleksei,

Please find result from appium console for driver.getPageSouce()

Also it is a Native app and from the eclipse console I do not get any error message.


#9

It is a Native app. Also I have mentioned the driver.getsourcePage in the previous message.


#10

@Bhagyashree_Panigrah wow. now we see 193 sec in response = pageSource is too large. Does this page contains many elements?


#11

Yes, it contains list of records. Is is feasible to identify the object in any way?


#12

@Bhagyashree_Panigrah try with same screen BUT with min possible number of objects. If it helps -> ask dev to reduce number of object in list. Load objects while user scrolling down.


#13

I had a discussion with developer they have already implemented the loading object on scrolling. Is there any other way around?