Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[Bug] Appium tests (iOS). UI elements are missing from page source XML representation with Xamarin 4.6 update #11026

Closed
ljoshenjka opened this issue Jun 12, 2020 · 10 comments
Closed

[Bug] Appium tests (iOS). UI elements are missing from page source XML representation with Xamarin 4.6 update #11026

ljoshenjka opened this issue Jun 12, 2020 · 10 comments
Assignees
@PureWeen
Labels
a/a11y 🔍 e/3 🕒 3 in-progress This issue has an associated pull request that may resolve it! p/iOS 🍎 t/bug 🐛
Projects
vCurrent (4.8.0)

Comments

@ljoshenjka
Copy link

Description

I am using Appium for test automation on Android/iOS apps build with Xamarin.Forms. Appium returns a XML representation of a page UI elements with some properties and gives ability to interact with it.
After updating Xamarin from 4.5 to 4.6 (4.6.0.800) some of the iOS (13) application pages returned by Appium are almost with all UI elements missing from XML page source representation. No issues observed on Android.

Steps to Reproduce

  1. Open application and inspect it with Appium GUI tool

Screenshot 2020-05-28 at 16 30 54

Expected Behavior

All the UI elements are returned in page source XML representation

Actual Behavior

Page source missing most of the page UI elements

Basic Information

  • Version with issue: Xamarin.Forms 4.6.0.800
  • Affected Devices: all iOS
  • Appium version: 1.17
  • Xcode version: 11.5
  • Desktop OS/version used to run Appium: macOS Catalina 10.15.4
@ljoshenjka ljoshenjka added s/unverified New report that has yet to be verified t/bug 🐛 labels Jun 12, 2020
@pauldipietro pauldipietro added this to New in Triage Jun 12, 2020
@hartez
Copy link
Contributor

hartez commented Jun 12, 2020

@ljoshenjka Your issue's Basic Information says all iOS devices are affected, but your description mentions iOS 13 specifically. Are you seeing this on other iOS versions?

@hartez hartez added the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Jun 12, 2020
@hartez hartez moved this from New to Needs Info in Triage Jun 12, 2020
@ljoshenjka
Copy link
Author

@hartez issue is not related to some specific iOS version. I guess I just wanted to point that it could be reproduced even with latest iOS 13.5.1

@samhouts
Copy link
Member

see also #6667

@PureWeen PureWeen self-assigned this Jun 15, 2020
@PureWeen PureWeen mentioned this issue Jun 16, 2020
Merged
2 tasks
@samhouts samhouts added the in-progress This issue has an associated pull request that may resolve it! label Jun 16, 2020
@PureWeen
Copy link
Contributor

@ljoshenjka do you have a repro? or can you post your XAML here?

@ljoshenjka
Copy link
Author

@PureWeen here is the xaml for the page from screenshot: https://gist.github.com/ljoshenjka/29bb667118d4322b8d436ccdd6fe0d60

@samhouts samhouts removed the s/needs-info ❓ A question has been asked that requires an answer before work can continue on this issue. label Jun 18, 2020
@samhouts samhouts moved this from Needs Info to New in Triage Jun 19, 2020
@samhouts samhouts added this to In Progress in 4.7.0 Jun 20, 2020
@samhouts samhouts removed this from In Progress in 4.7.0 Jun 25, 2020
@samhouts samhouts added e/3 🕒 3 and removed s/unverified New report that has yet to be verified labels Jun 26, 2020
@samhouts samhouts moved this from New to Ready For Work in Triage Jun 26, 2020
@samhouts samhouts added this to To do in iOS Ready For Work Jun 26, 2020
@samhouts samhouts removed this from Ready For Work in Triage Jun 26, 2020
@adamhill
Copy link

adamhill commented Jul 9, 2020 •
edited
Loading

I would like to leave a piece of anecdotal information about this bug.

Us on the team at Paycor had problems like this with Xamarin and Appium quite frequently, mainly with finding children / data in Listviews. It was universally fixed with setting AutomationProperties.IsInAccessibleTree to false & quite repeatable.

Terrible for A11y but leadership did not have that as a priority.

We were on XF 3.6.x and Appium 1.15 & tested on iOS 13, 12, 11, 10, 9.

@PureWeen
Copy link
Contributor

The nuget for this Issue is here
https://dev.azure.com/xamarin/public/_build/results?buildId=21211&view=artifacts&type=publishedArtifacts

If anyone wants to test and let me know if that fixes for you

@samhouts samhouts added this to In Progress in Accessibility Jul 13, 2020
iOS Ready For Work automation moved this from To do to Done Jul 20, 2020
Accessibility automation moved this from In Progress to Done Jul 20, 2020
@alallo
Copy link

alallo commented Jul 24, 2020

@PureWeen that fixed the issue for us. Thanks

@srikcgaa2
Copy link

srikcgaa2 commented Jul 24, 2020 •
edited
Loading

This unofficial nuget fixes many of our issues as well on iOS, including the Issue 11392. Any update on which version of Xamarin.Forms this will be available (4.7 or 4.8) and tentatively when we can expect this in an official Xamarin.Forms release?

@alallo
Copy link

alallo commented Jul 24, 2020

It's already available in the latest 4.8 pre release version if you want to test it

@samhouts samhouts added this to In Progress in vCurrent (4.8.0) Jul 30, 2020
@samhouts samhouts moved this from In Progress to Done in vCurrent (4.8.0) Jul 30, 2020
@samhouts samhouts removed this from Done in iOS Ready For Work Aug 19, 2020
@samhouts samhouts removed this from Done in Accessibility Aug 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@PureWeen PureWeen

Labels
a/a11y 🔍 e/3 🕒 3 in-progress This issue has an associated pull request that may resolve it! p/iOS 🍎 t/bug 🐛
Projects
No open projects
vCurrent (4.8.0)
  
Done
Milestone
No milestone
Development

No branches or pull requests
7 participants
@adamhill @hartez @alallo @PureWeen @samhouts @srikcgaa2 @ljoshenjka