[ci-scan] Android SafeAreaPerEdgeValidation UI test repeatedly fails
- Dominant language
- C#
- Stars
- 23.3k
- Forks
- 2k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 297
Description
## Summary
SafeAreaPerEdgeValidation repeatedly fails on the Android API 36 UI-test leg.
## Build Information
- **Pipeline**: maui-pr-uitests
- **Build**: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1579258
- **Build ID**: 1579258
- **Branch**: main
- **First seen**: 2026-08-24
- **Occurrences**: 7 in last 10 builds
## Affected Legs
- Android API 36 Pixel 3 XL emulator, CoreCLR, Release
## Error Message
```text
2026-09-02T18:40:58.3979609Z Failed SafeAreaPerEdgeValidation [28 s]
```
## Recommended Action
Investigate per-edge inset application in src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue28986.cs and Issue28986_ContentPage.cs together with the Android safe-area implementation; reproduce on API 36.
Contributor guide
Research direction
Start by reproducing SafeAreaPerEdgeValidation on the Android API 36 Pixel 3 XL emulator in the maui-pr-uitests pipeline. Read src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue28986.cs and Issue28986_ContentPage.cs, then trace the Android safe-area implementation. Done means the test passes reliably across the affected UI-test leg and per-edge insets are applied correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, csharp
- Domain
- mobile, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100