dotnet / dotnet/maui

[ci-scan-net11] Android SafeArea keyboard resize assertions fail in UI tests

Open
#37,558 0 comments 0 reactions 0 assignees View on GitHub
ci-scan-net11
Dominant language
C#
Stars
23.3k
Forks
2k
Avg merge
1d 15h
Merged PRs (30d)
290

Description

## Summary
The Android SafeArea UI test repeatedly reports that the content grid does not shrink when the keyboard appears.

## Build Information
- **Pipeline**: maui-pr-uitests
- **Build**: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1554813
- **Build ID**: 1554813
- **Branch**: net11.0
- **First seen**: 2026-08-12
- **Occurrences**: 10 in last 10 builds

## Affected Legs
- Controls SafeAreaEdges / Android API 36 / Pixel 3 XL

## Error Message
```text
2026-08-16T16:38:41.9965788Z 1) ContentGrid should shrink when keyboard is showing with SafeAreaEdges=All
2026-08-16T16:38:41.9966349Z Expected: less than 2705
2026-08-16T16:38:41.9966486Z But was: 2705
```

## Recommended Action
Investigate keyboard-driven SafeArea relayout on Android and the assertions in `src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue28986_ContentPage.cs`; verify the content grid is remeasured after keyboard visibility and SafeAreaEdges changes.

Contributor guide

Open the contributing guide

Research direction

Start with src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue28986_ContentPage.cs and reproduce the SafeArea UI test from the maui-pr-uitests Android API 36 failure. Trace the keyboard visibility and SafeAreaEdges changes around the content-grid assertions. Done means the content grid is remeasured after those changes and the affected assertions pass on the Android test leg.

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
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.