[ci-scan] Recurring Android CollectionViewHeaderShouldNotScroll stale-element failure
Open
Nobody has claimed this yet.
ci-scan
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 296
Description
Summary
CollectionViewHeaderShouldNotScroll has failed in two of the last ten main builds on Android while interacting with a stale UI element.
Build Information
- Pipeline: maui-pr-uitests
- Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1574142
- Build ID: 1574142
- Branch: main
- First seen: 2026-08-24
- Occurrences: 2 in last 10 builds
Affected Legs
- Android UI tests / Android emulator
Error Message
2026-08-30T13:49:10.5331188Z Failed CollectionViewHeaderShouldNotScroll [3 s]
Recommended Action
Investigate the Android CollectionView header test's element lifetime around scrolling and reacquire the element after any UI-tree update before reading or interacting with it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Android UI test named CollectionViewHeaderShouldNotScroll in the maui-pr-uitests pipeline and inspect the failure log around scrolling and the stale-element error. Done means the test no longer fails from a stale UI element across repeated Android runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100