Closed Bug 1769510 Opened 4 years ago Closed 4 years ago

Recent regression in GV release 102.0.20220514065807: UIAutomator unable to locate widget content elements in all app clients (UI Tests on mobile apps failing)

Categories

(Core :: Disability Access APIs, defect, P1)

ARM64
All
defect

Tracking

()

RESOLVED FIXED
102 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox100 --- unaffected
firefox101 --- unaffected
firefox102 blocking fixed

People

(Reporter: aryx, Unassigned)

References

(Regression)

Details

(Keywords: regression)

+++ This bug was initially created as a clone of Bug #1760880 +++

Assuming this is GeckoView related as there is nothing else on A-C upgrade that is causing issues.

So therefore last working geckoview version: 102.0.20220513093538
Broken geckoview version: 102.0.20220514065807

What changed in this update?

https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0914de230f91d8a035607e9807ef381688294654&tochange=64cf24289e449ea3e5b97c0f18e27eaf462f822c

UiAutomator which we use for locating elements in Gecko on Android is not working, thus all interactions with web content (e.g, clicking a link) are not working.

Example Espresso/UI Automator test: https://github.com/mozilla-mobile/fenix/blob/master/app/src/androidTest/java/org/mozilla/fenix/ui/DownloadTest.kt#L68

Set release status flags based on info from the regressing bug 1758540

:eeejay, since you are the author of the regressor, bug 1758540, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(eitan)
Severity: -- → S1
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(eitan)
Priority: -- → P1
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
No longer blocks: 1771288
You need to log in before you can comment on or make changes to this bug.