Skip to content

[Android] Fix empty space above TabBar after navigating back when TabBar visibility is toggled#34324

Merged
kubaflo merged 11 commits intodotnet:inflight/currentfrom
praveenkumarkarunanithi:fix-33703
Apr 6, 2026
Merged

[Android] Fix empty space above TabBar after navigating back when TabBar visibility is toggled#34324
kubaflo merged 11 commits intodotnet:inflight/currentfrom
praveenkumarkarunanithi:fix-33703

Conversation

@praveenkumarkarunanithi
Copy link
Copy Markdown
Contributor

@praveenkumarkarunanithi praveenkumarkarunanithi commented Mar 4, 2026 •
edited
Loading

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue.
Thank you!

Root Cause

When Shell.TabBarIsVisible is set to false, Android hides the TabBar by setting its visibility to Gone. As a result, the page content expands to occupy the full screen, including the area previously used by the TabBar. At this point, the safe area padding is calculated correctly based on the full screen height.
When navigating back and the TabBar becomes visible again, Android reduces the height of the page content to accommodate the TabBar. However, Android does not automatically re-apply window insets when a sibling view changes from Gone to Visible. Because of this, the previously calculated bottom padding (based on the full screen height) remains unchanged, leaving an empty space between the page content and the TabBar.

Description of Change

When the TabBar transitions from Gone to Visible, the fix explicitly requests Android to re-apply window insets for the currently displayed page.
The request is posted to run after the layout pass completes, ensuring the page size has been updated before safe area padding is recalculated. An additional check ensures that the page is still attached to the window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update, the safe area padding is recalculated using the updated page height, eliminating the empty space above the TabBar. The fix is scoped to run only when the TabBar transitions from hidden to visible.

Issues Fixed

Fixes #33703
Fixes #34256

Tested the behaviour in the following platforms

  • Android
  • Windows
  • iOS
  • Mac

Note

The UI test is added for Android only as this issue is specific to Android — the empty space above the TabBar after navigating back only reproduces on Android.

Output Video

Before Issue Fix After Issue Fix
Beforefix.mov
Afterfix.mov

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 4, 2026 •
edited
Loading

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://github.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 34324

Or

  • Run remotely in PowerShell:
iex "& { $(irm https://github.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 34324"

@dotnet-policy-service dotnet-policy-service Bot added the partner/syncfusion Issues / PR's with Syncfusion collaboration label Mar 4, 2026
@karthikraja-arumugam karthikraja-arumugam added the community ✨ Community Contribution label Mar 4, 2026
@jfversluis jfversluis mentioned this pull request Mar 4, 2026
Merged
praveenkumarkarunanithi and others added 6 commits March 11, 2026 12:38
@praveenkumarkarunanithi
updating test
27fd7c2
@praveenkumarkarunanithi
Update ShellItemRenderer.cs
9d5e35b
@praveenkumarkarunanithi
Update Issue33703.cs
c1d0abf
@praveenkumarkarunanithi
updated test and base image
cf538ac
@jfversluis @praveenkumarkarunanithi
Fix review findings from multi-model review
b5cb805 
- Fix .xaml.cs matching: strip .xaml extension for HostApp file matching
- Relax file naming: only flag files in Issues/ that start with Issue
- AutomationId: bidirectional check, reverse direction is informational
- Wait check: per-interaction instead of file-level
- Unit test helpers: only flag missing test methods if filename contains Test
- Fix duplicate numbering in copilot-instructions.md (8,8,9,9 → 8,9,10,10)
- Skip [Issue()] check on .xaml files (attribute lives in code-behind)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@praveenkumarkarunanithi
Delete .github/skills/evaluate-pr-tests/scripts/Gather-TestContext.ps1
653056a
@sheiksyedm sheiksyedm marked this pull request as ready for review March 13, 2026 10:29
Copilot AI review requested due to automatic review settings March 13, 2026 10:29
@sheiksyedm sheiksyedm added platform/android area-controls-shell Shell Navigation, Routes, Tabs, Flyout labels Mar 13, 2026
@sheiksyedm
Copy link
Copy Markdown
Contributor

sheiksyedm commented Mar 13, 2026

/azp run maui-pr-uitests , maui-pr-devicetests

@azure-pipelines
Copy link
Copy Markdown

azure-pipelines Bot commented Mar 13, 2026

Azure Pipelines successfully started running 2 pipeline(s).

Copilot AI reviewed Mar 13, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes an Android Shell regression where content retains stale bottom safe-area padding after the TabBar transitions from Gone → Visible (e.g., navigating back from a page that hides the TabBar), leaving empty space above the TabBar.

Changes:

  • Android: when the TabBar becomes visible again, explicitly re-request window insets on the displayed page’s platform view after layout (ViewCompat.RequestApplyInsets).
  • Adds a new Android UI test (Issue33703) and corresponding HostApp repro page to validate the layout after back navigation.
  • Adds an Android screenshot baseline for the new test.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 3 comments.

File Description
src/Controls/src/Core/Compatibility/Handlers/Shell/Android/ShellItemRenderer.cs Requests insets after TabBar Gone → Visible to refresh safe-area padding and remove the empty gap.
src/Controls/tests/TestCases.HostApp/Issues/Issue33703.cs Adds a Shell-based repro with a ScrollView and a detail page that hides the TabBar.
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33703.cs Adds an Android-only Appium test that navigates, returns, scrolls to bottom, and verifies via screenshot.
src/Controls/tests/TestCases.Android.Tests/snapshots/android/TabBarShouldNotHaveEmptySpaceAfterNavigatingBack.png Adds the screenshot baseline for the new Android test.

Comment thread src/Controls/tests/TestCases.HostApp/Issues/Issue33703.cs Outdated
Comment thread src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33703.cs Outdated
Comment thread src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33703.cs Outdated
This was referenced Mar 13, 2026
Open
Open
Closed
Open
Open
praveenkumarkarunanithi and others added 2 commits March 16, 2026 12:50
@praveenkumarkarunanithi
Potential fix for pull request finding
9e67230 
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@praveenkumarkarunanithi
Update Issue33703.cs
b7f4f78
PureWeen pushed a commit that referenced this pull request Mar 18, 2026
@jfversluis
@github-actions @kubaflo
Add evaluate-pr-tests skill for test quality evaluation (#34329)
c1b4a01 
## Description

Adds a new Copilot skill (`evaluate-pr-tests`) that evaluates the
quality, coverage, and appropriateness of tests added in PRs.

## Why This Is Useful

**Problem:** When reviewing PRs, evaluating test quality is one of the
most time-consuming and inconsistent parts of the process. Common issues
slip through:

- Tests that only verify a page loads but never exercise the actual fix
- UI tests for behavior that could be caught by a unit test (which runs
in seconds vs minutes)
- Missing edge cases (null inputs, boundary values, repeated actions)
that lead to regressions later
- Convention violations (wrong base class, missing attributes, obsolete
APIs) that cause CI failures
- Flaky patterns (arbitrary delays, missing `WaitForElement`) that waste
CI time

These issues are tedious to catch manually and easy to miss — especially
across 4 platforms, 4 test types (unit, XAML, device, UI), and hundreds
of existing test patterns.

**Solution:** This skill automates the mechanical checks and guides the
agent through deeper analysis:

1. **Automated (script):** File categorization, convention compliance,
anti-pattern detection, AutomationId consistency, existing similar test
search, platform scope analysis
2. **Agent-guided (SKILL.md):** Fix coverage analysis, edge case gap
identification, test type recommendation (prefer unit > XAML > device >
UI), assertion quality review

**Real-world example:** Running against PR #34324 (Android Shell TabBar
fix), the skill:
- ✅ Correctly identified 1 fix file + 1 UI test + 1 HostApp page + 1
snapshot
- ⚠️ Flagged an inline `#if` platform directive (real convention
violation)
- ℹ️ Noted 3 HostApp AutomationIds not exercised by the test
(informational)
- ✅ Found existing Shell tests for cross-reference
- ✅ Identified this as Android-only based on fix file paths

**Quality bar:** This skill went through 3 rounds of multi-model review
(10 total reviews across Opus, GPT-5.1, Gemini, Sonnet 4.5) to catch
regex bugs, false positive/negative edge cases, and documentation
mismatches.

## Evaluation Criteria (9 checks)

| # | Criterion | What It Checks |
|---|-----------|---------------|
| 1 | **Fix Coverage** | Does the test exercise the actual code paths
changed by the fix? |
| 2 | **Edge Cases & Gaps** | Boundary conditions, null handling,
async/timing, repeated actions |
| 3 | **Test Type Appropriateness** | Could a lighter test type work?
(unit > XAML > device > UI) |
| 4 | **Convention Compliance** | Naming, attributes, base classes,
obsolete APIs |
| 5 | **Flakiness Risk** | Delays, missing WaitForElement, screenshot
hygiene |
| 6 | **Duplicate Coverage** | Does a similar test already exist? |
| 7 | **Platform Scope** | Does test coverage match platforms affected
by the fix? |
| 8 | **Assertion Quality** | Are assertions specific enough to catch
regressions? |
| 9 | **Fix-Test Alignment** | Do test and fix target the same code
paths? |

## Components

- **`SKILL.md`** — Evaluation criteria with decision trees, examples,
and structured report template
- **`Gather-TestContext.ps1`** — Automated convention checks,
anti-pattern detection, AutomationId consistency, platform scope
analysis
- **`copilot-instructions.md`** — Skill registration with trigger
phrases

## Usage

```bash
# Auto-detect PR context
pwsh .github/skills/evaluate-pr-tests/scripts/Gather-TestContext.ps1

# Or ask the agent
# "evaluate the tests in this PR"
# "are these tests good enough?"
# "review test quality for PR #XXXXX"
```

- Fixes #34139

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Jakub Florkowski <42434498+kubaflo@users.noreply.github.com>
@MauiBot MauiBot added the s/agent-review-incomplete AI agent could not complete all phases (blocker, timeout, error) label Mar 20, 2026
@praveenkumarkarunanithi
Copy link
Copy Markdown
Contributor Author

praveenkumarkarunanithi commented Mar 24, 2026

Looks like the test if failing

Fixed the Issue string mismatch — test should pass now.

@MauiBot MauiBot added s/agent-review-incomplete AI agent could not complete all phases (blocker, timeout, error) s/agent-approved AI agent recommends approval - PR fix is correct and optimal and removed s/agent-changes-requested AI agent recommends changes - found a better alternative or issues s/agent-review-incomplete AI agent could not complete all phases (blocker, timeout, error) labels Mar 24, 2026
KarthikRajaKalaimani pushed a commit to KarthikRajaKalaimani/maui that referenced this pull request Mar 30, 2026
@jfversluis
@github-actions @kubaflo @KarthikRajaKalaimani
Add evaluate-pr-tests skill for test quality evaluation (dotnet#34329)
b268c7d 
## Description

Adds a new Copilot skill (`evaluate-pr-tests`) that evaluates the
quality, coverage, and appropriateness of tests added in PRs.

## Why This Is Useful

**Problem:** When reviewing PRs, evaluating test quality is one of the
most time-consuming and inconsistent parts of the process. Common issues
slip through:

- Tests that only verify a page loads but never exercise the actual fix
- UI tests for behavior that could be caught by a unit test (which runs
in seconds vs minutes)
- Missing edge cases (null inputs, boundary values, repeated actions)
that lead to regressions later
- Convention violations (wrong base class, missing attributes, obsolete
APIs) that cause CI failures
- Flaky patterns (arbitrary delays, missing `WaitForElement`) that waste
CI time

These issues are tedious to catch manually and easy to miss — especially
across 4 platforms, 4 test types (unit, XAML, device, UI), and hundreds
of existing test patterns.

**Solution:** This skill automates the mechanical checks and guides the
agent through deeper analysis:

1. **Automated (script):** File categorization, convention compliance,
anti-pattern detection, AutomationId consistency, existing similar test
search, platform scope analysis
2. **Agent-guided (SKILL.md):** Fix coverage analysis, edge case gap
identification, test type recommendation (prefer unit > XAML > device >
UI), assertion quality review

**Real-world example:** Running against PR dotnet#34324 (Android Shell TabBar
fix), the skill:
- ✅ Correctly identified 1 fix file + 1 UI test + 1 HostApp page + 1
snapshot
- ⚠️ Flagged an inline `#if` platform directive (real convention
violation)
- ℹ️ Noted 3 HostApp AutomationIds not exercised by the test
(informational)
- ✅ Found existing Shell tests for cross-reference
- ✅ Identified this as Android-only based on fix file paths

**Quality bar:** This skill went through 3 rounds of multi-model review
(10 total reviews across Opus, GPT-5.1, Gemini, Sonnet 4.5) to catch
regex bugs, false positive/negative edge cases, and documentation
mismatches.

## Evaluation Criteria (9 checks)

| # | Criterion | What It Checks |
|---|-----------|---------------|
| 1 | **Fix Coverage** | Does the test exercise the actual code paths
changed by the fix? |
| 2 | **Edge Cases & Gaps** | Boundary conditions, null handling,
async/timing, repeated actions |
| 3 | **Test Type Appropriateness** | Could a lighter test type work?
(unit > XAML > device > UI) |
| 4 | **Convention Compliance** | Naming, attributes, base classes,
obsolete APIs |
| 5 | **Flakiness Risk** | Delays, missing WaitForElement, screenshot
hygiene |
| 6 | **Duplicate Coverage** | Does a similar test already exist? |
| 7 | **Platform Scope** | Does test coverage match platforms affected
by the fix? |
| 8 | **Assertion Quality** | Are assertions specific enough to catch
regressions? |
| 9 | **Fix-Test Alignment** | Do test and fix target the same code
paths? |

## Components

- **`SKILL.md`** — Evaluation criteria with decision trees, examples,
and structured report template
- **`Gather-TestContext.ps1`** — Automated convention checks,
anti-pattern detection, AutomationId consistency, platform scope
analysis
- **`copilot-instructions.md`** — Skill registration with trigger
phrases

## Usage

```bash
# Auto-detect PR context
pwsh .github/skills/evaluate-pr-tests/scripts/Gather-TestContext.ps1

# Or ask the agent
# "evaluate the tests in this PR"
# "are these tests good enough?"
# "review test quality for PR #XXXXX"
```

- Fixes dotnet#34139

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Jakub Florkowski <42434498+kubaflo@users.noreply.github.com>
@MauiBot MauiBot added s/agent-changes-requested AI agent recommends changes - found a better alternative or issues and removed s/agent-approved AI agent recommends approval - PR fix is correct and optimal labels Apr 3, 2026
@dotnet dotnet deleted a comment from MauiBot Apr 5, 2026
@dotnet dotnet deleted a comment from MauiBot Apr 5, 2026
@MauiBot
Copy link
Copy Markdown
Collaborator

MauiBot commented Apr 5, 2026

🚦 Gate - Test Before and After Fix

📊 Expand Full Gate — 3a1b816 · Update Issue33703.cs

Gate Result: ✅ PASSED

Platform: ANDROID · Base: main · Merge base: 794a9fa6

Test Without Fix (expect FAIL) With Fix (expect PASS)
🖥️ Issue33703 Issue33703 ✅ FAIL — 813s ✅ PASS — 1327s
🔴 Without fix — 🖥️ Issue33703: FAIL ✅ · 813s 
  Determining projects to restore...
  Restored /home/vsts/work/1/s/src/Controls/src/Core/Controls.Core.csproj (in 9.6 sec).
  Restored /home/vsts/work/1/s/src/Controls/Maps/src/Controls.Maps.csproj (in 9.55 sec).
  Restored /home/vsts/work/1/s/src/Controls/Foldable/src/Controls.Foldable.csproj (in 583 ms).
  Restored /home/vsts/work/1/s/src/Graphics/src/Graphics/Graphics.csproj (in 10 ms).
  Restored /home/vsts/work/1/s/src/Essentials/src/Essentials.csproj (in 18 ms).
  Restored /home/vsts/work/1/s/src/Core/src/Core.csproj (in 44 ms).
  Restored /home/vsts/work/1/s/src/Core/maps/src/Maps.csproj (in 26 ms).
  Restored /home/vsts/work/1/s/src/BlazorWebView/src/Maui/Microsoft.AspNetCore.Components.WebView.Maui.csproj (in 3.76 sec).
  Restored /home/vsts/work/1/s/src/Controls/src/Xaml/Controls.Xaml.csproj (in 26 ms).
  Restored /home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj (in 3.2 sec).
  1 of 11 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0-android36.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Essentials/Debug/net10.0-android36.0/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Core/Debug/net10.0-android36.0/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Maps -> /home/vsts/work/1/s/artifacts/bin/Maps/Debug/net10.0-android36.0/Microsoft.Maui.Maps.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.Core/Debug/net10.0-android36.0/Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Xaml -> /home/vsts/work/1/s/artifacts/bin/Controls.Xaml/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Xaml.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> /home/vsts/work/1/s/artifacts/bin/Microsoft.AspNetCore.Components.WebView.Maui/Debug/net10.0-android36.0/Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.Foldable/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Foldable.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.Maps/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Maps.dll
  Controls.TestCases.HostApp -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Controls.TestCases.HostApp.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Microsoft.AspNetCore.Components.WebView.Maui -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Xaml -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Xaml.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Maps.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Foldable.dll
  Controls.Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Maps.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:08:41.27
Broadcasting: Intent { act=android.intent.action.CLOSE_SYSTEM_DIALOGS flg=0x400000 }
Broadcast completed: result=0
Broadcasting: Intent { act=android.intent.action.CLOSE_SYSTEM_DIALOGS flg=0x400000 }
Broadcast completed: result=0
  Determining projects to restore...
  Restored /home/vsts/work/1/s/src/TestUtils/src/VisualTestUtils/VisualTestUtils.csproj (in 1.28 sec).
  Restored /home/vsts/work/1/s/src/TestUtils/src/VisualTestUtils.MagickNet/VisualTestUtils.MagickNet.csproj (in 13.83 sec).
  Restored /home/vsts/work/1/s/src/Controls/tests/TestCases.Android.Tests/Controls.TestCases.Android.Tests.csproj (in 15.31 sec).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.Core/UITest.Core.csproj (in 7 ms).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.Appium/UITest.Appium.csproj (in 2 ms).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.NUnit/UITest.NUnit.csproj (in 1.59 sec).
  Restored /home/vsts/work/1/s/src/Controls/tests/CustomAttributes/Controls.CustomAttributes.csproj (in 5 ms).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.Analyzers/UITest.Analyzers.csproj (in 4.66 sec).
  5 of 13 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Essentials/Debug/net10.0/Microsoft.Maui.Essentials.dll
  Controls.CustomAttributes -> /home/vsts/work/1/s/artifacts/bin/Controls.CustomAttributes/Debug/net10.0/Controls.CustomAttributes.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Core/Debug/net10.0/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.Core/Debug/net10.0/Microsoft.Maui.Controls.dll
  UITest.Core -> /home/vsts/work/1/s/artifacts/bin/UITest.Core/Debug/net10.0/UITest.Core.dll
  VisualTestUtils -> /home/vsts/work/1/s/artifacts/bin/VisualTestUtils/Debug/netstandard2.0/VisualTestUtils.dll
  UITest.NUnit -> /home/vsts/work/1/s/artifacts/bin/UITest.NUnit/Debug/net10.0/UITest.NUnit.dll
  VisualTestUtils.MagickNet -> /home/vsts/work/1/s/artifacts/bin/VisualTestUtils.MagickNet/Debug/netstandard2.0/VisualTestUtils.MagickNet.dll
  UITest.Appium -> /home/vsts/work/1/s/artifacts/bin/UITest.Appium/Debug/net10.0/UITest.Appium.dll
  UITest.Analyzers -> /home/vsts/work/1/s/artifacts/bin/UITest.Analyzers/Debug/netstandard2.0/UITest.Analyzers.dll
  Controls.TestCases.Android.Tests -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
Test run for /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll (.NETCoreApp,Version=v10.0)
VSTest version 18.0.1 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
/home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.8.2+699d445a1a (64-bit .NET 10.0.0)
[xUnit.net 00:00:00.17]   Discovering: Controls.TestCases.Android.Tests
[xUnit.net 00:00:00.54]   Discovered:  Controls.TestCases.Android.Tests
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
   NUnit3TestExecutor discovered 1 of 1 NUnit test cases using Current Discovery mode, Non-Explicit run
>>>>> 04/05/2026 22:19:47 FixtureSetup for Issue33703(Android)
>>>>> 04/05/2026 22:19:50 TabBarShouldNotHaveEmptySpaceAfterNavigatingBack Start
>>>>> 04/05/2026 22:20:04 TabBarShouldNotHaveEmptySpaceAfterNavigatingBack Stop
>>>>> 04/05/2026 22:20:04 Log types: logcat, bugreport, server
  Failed TabBarShouldNotHaveEmptySpaceAfterNavigatingBack [15 s]
  Error Message:
   VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: TabBarShouldNotHaveEmptySpaceAfterNavigatingBack.png (15.40% difference)
If the correct baseline has changed (this isn't a a bug), then update the baseline image.
See test attachment or download the build artifacts to get the new snapshot file.

More info: https://aka.ms/visual-test-workflow

  Stack Trace:
     at VisualTestUtils.VisualRegressionTester.Fail(String message) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 162
   at VisualTestUtils.VisualRegressionTester.VerifyMatchesSnapshot(String name, ImageSnapshot actualImage, String environmentName, ITestContext testContext) in /_/src/TestUtils/src/VisualTestUtils/VisualRegressionTester.cs:line 123
   at Microsoft.Maui.TestCases.Tests.UITest.<VerifyScreenshot>g__Verify|13_0(String name, <>c__DisplayClass13_0&) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 477
   at Microsoft.Maui.TestCases.Tests.UITest.VerifyScreenshot(String name, Nullable`1 retryDelay, Nullable`1 retryTimeout, Int32 cropLeft, Int32 cropRight, Int32 cropTop, Int32 cropBottom, Double tolerance) in /_/src/Controls/tests/TestCases.Shared.Tests/UITest.cs:line 309
   at Microsoft.Maui.TestCases.Tests.Issues.Issue33703.TabBarShouldNotHaveEmptySpaceAfterNavigatingBack() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue33703.cs:line 25
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

NUnit Adapter 4.5.0.0: Test execution complete

Total tests: 1
     Failed: 1
Test Run Failed.
 Total time: 1.4155 Minutes
🟢 With fix — 🖥️ Issue33703: PASS ✅ · 1327s

(truncated to last 15,000 chars)

pp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010: --- End of stack trace from previous location --- [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at AndroidDeviceExtensions.PushAndInstallPackageAsync(AndroidDevice device, PushAndInstallCommand command, CancellationToken token) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at AndroidDeviceExtensions.PushAndInstallPackageAsync(AndroidDevice device, PushAndInstallCommand command, CancellationToken token) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.InstallPackage(Boolean installed) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.InstallPackage(Boolean installed) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.RunInstall() [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]

Build FAILED.

/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010: Mono.AndroidTools.InstallFailedException: Unexpected install output: cmd: Failure calling service package: Broken pipe (32) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:  [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Mono.AndroidTools.Internal.AdbOutputParsing.CheckInstallSuccess(String output, String packageName) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Mono.AndroidTools.AndroidDevice.<>c__DisplayClass105_0.<InstallPackage>b__0(Task`1 t) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010: --- End of stack trace from previous location --- [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010: --- End of stack trace from previous location --- [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at AndroidDeviceExtensions.PushAndInstallPackageAsync(AndroidDevice device, PushAndInstallCommand command, CancellationToken token) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at AndroidDeviceExtensions.PushAndInstallPackageAsync(AndroidDevice device, PushAndInstallCommand command, CancellationToken token) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.InstallPackage(Boolean installed) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.InstallPackage(Boolean installed) [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
/home/vsts/work/1/s/.dotnet/packs/Microsoft.Android.Sdk.Linux/36.1.2/tools/Xamarin.Android.Common.Debugging.targets(333,5): error ADB0010:    at Xamarin.Android.Tasks.FastDeploy.RunInstall() [/home/vsts/work/1/s/src/Controls/tests/TestCases.HostApp/Controls.TestCases.HostApp.csproj::TargetFramework=net10.0-android]
    0 Warning(s)
    1 Error(s)

Time Elapsed 00:11:01.87
* daemon not running; starting now at tcp:5037
* daemon started successfully
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0-android36.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Essentials/Debug/net10.0-android36.0/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Core/Debug/net10.0-android36.0/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Maps -> /home/vsts/work/1/s/artifacts/bin/Maps/Debug/net10.0-android36.0/Microsoft.Maui.Maps.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.Core/Debug/net10.0-android36.0/Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Xaml -> /home/vsts/work/1/s/artifacts/bin/Controls.Xaml/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Xaml.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> /home/vsts/work/1/s/artifacts/bin/Microsoft.AspNetCore.Components.WebView.Maui/Debug/net10.0-android36.0/Microsoft.AspNetCore.Components.WebView.Maui.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.Foldable/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Foldable.dll
  Controls.Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.Maps/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Maps.dll
  Controls.TestCases.HostApp -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Controls.TestCases.HostApp.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Maps.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Xaml -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Xaml.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Maps -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Maps.dll
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Foldable.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:08:38.05
Broadcasting: Intent { act=android.intent.action.CLOSE_SYSTEM_DIALOGS flg=0x400000 }
Broadcast completed: result=0
Broadcasting: Intent { act=android.intent.action.CLOSE_SYSTEM_DIALOGS flg=0x400000 }
Broadcast completed: result=0
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.CustomAttributes -> /home/vsts/work/1/s/artifacts/bin/Controls.CustomAttributes/Debug/net10.0/Controls.CustomAttributes.dll
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Essentials/Debug/net10.0/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Core -> /home/vsts/work/1/s/artifacts/bin/Core/Debug/net10.0/Microsoft.Maui.dll
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13750570
  Controls.Core -> /home/vsts/work/1/s/artifacts/bin/Controls.Core/Debug/net10.0/Microsoft.Maui.Controls.dll
  UITest.Core -> /home/vsts/work/1/s/artifacts/bin/UITest.Core/Debug/net10.0/UITest.Core.dll
  VisualTestUtils -> /home/vsts/work/1/s/artifacts/bin/VisualTestUtils/Debug/netstandard2.0/VisualTestUtils.dll
  UITest.NUnit -> /home/vsts/work/1/s/artifacts/bin/UITest.NUnit/Debug/net10.0/UITest.NUnit.dll
  VisualTestUtils.MagickNet -> /home/vsts/work/1/s/artifacts/bin/VisualTestUtils.MagickNet/Debug/netstandard2.0/VisualTestUtils.MagickNet.dll
  UITest.Appium -> /home/vsts/work/1/s/artifacts/bin/UITest.Appium/Debug/net10.0/UITest.Appium.dll
  UITest.Analyzers -> /home/vsts/work/1/s/artifacts/bin/UITest.Analyzers/Debug/netstandard2.0/UITest.Analyzers.dll
  Controls.TestCases.Android.Tests -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
Test run for /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll (.NETCoreApp,Version=v10.0)
VSTest version 18.0.1 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
/home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.8.2+699d445a1a (64-bit .NET 10.0.0)
[xUnit.net 00:00:00.18]   Discovering: Controls.TestCases.Android.Tests
[xUnit.net 00:00:00.40]   Discovered:  Controls.TestCases.Android.Tests
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.Android.Tests/Debug/net10.0/Controls.TestCases.Android.Tests.dll
   NUnit3TestExecutor discovered 1 of 1 NUnit test cases using Current Discovery mode, Non-Explicit run
>>>>> 04/05/2026 22:42:01 FixtureSetup for Issue33703(Android)
>>>>> 04/05/2026 22:42:03 TabBarShouldNotHaveEmptySpaceAfterNavigatingBack Start
>>>>> 04/05/2026 22:42:14 TabBarShouldNotHaveEmptySpaceAfterNavigatingBack Stop
  Passed TabBarShouldNotHaveEmptySpaceAfterNavigatingBack [11 s]
NUnit Adapter 4.5.0.0: Test execution complete

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 33.2856 Seconds
📁 Fix files reverted (2 files)
  • eng/pipelines/ci-copilot.yml
  • src/Controls/src/Core/Compatibility/Handlers/Shell/Android/ShellItemRenderer.cs

@MauiBot
Copy link
Copy Markdown
Collaborator

MauiBot commented Apr 6, 2026

🤖 AI Summary

📊 Expand Full Review — 3a1b816 · Update Issue33703.cs
🔍 Pre-Flight — Context & Validation

Issue: #33703 - Empty space appears above TabBar after navigating back when TabBar visibility is toggled
PR: #34324 - [Android] Fix empty space above TabBar after navigating back when TabBar visibility is toggled
Platforms Affected: Android (issue is Android-only)
Files Changed: 1 implementation, 2 test files, 1 snapshot

Key Findings

  • Root Cause: When Shell.TabBarIsVisible = false, the TabBar is set to ViewStates.Gone on Android, and content expands to full screen. When navigating back and the TabBar becomes Visible again, Android does NOT re-dispatch window insets to child views, leaving stale bottom padding that creates empty space above the TabBar.
  • Regression since .NET 10 RC2, worked in .NET MAUI 9.0.90 SR9
  • Fix Location: ShellItemRenderer.UpdateTabBarVisibility() in Android Shell compatibility renderer
  • Fix Approach: After a Gone → Visible TabBar transition, use ViewCompat.RequestApplyInsets() (posted via platformView.Post()) to force re-dispatch of window insets, triggering safe-area padding recalculation with the updated page height
  • Guards: wasGone && showTabs (only on relevant transition) + platformView.IsAttachedToWindow (avoid unnecessary calls)
  • Test: Screenshot test TabBarShouldNotHaveEmptySpaceAfterNavigatingBack — navigates to detail page (TabBar hidden), navigates back, scrolls to bottom, verifies screenshot
  • Review Comments (all resolved): Minor grammar fixes requested by copilot-pull-request-reviewer (already resolved in later commits)
  • Gate: ✅ PASSED — test FAIL without fix, PASS with fix (confirmed by MauiBot comment)
  • Related issue: Also fixes Grid with SafeAreaEdges=Container has incorrect size when tab bar appears #34256

Fix Candidates

# Source Approach Test Result Files Changed Notes
PR PR #34324 On Gone→Visible tab transition, call ViewCompat.RequestApplyInsets(platformView) via Post() after layout pass ✅ PASSED (Gate) ShellItemRenderer.cs Requires AndroidX.Core.View import
🔧 Fix — Analysis & Comparison

Fix Candidates

# Source Approach Test Result Files Changed Notes
PR PR #34324 On Gone→Visible, ViewCompat.RequestApplyInsets(platformView) via Post() on displayed page's platform view ✅ PASSED (Gate) ShellItemRenderer.cs Simplest — 16 lines added
1 try-fix (claude-opus-4.6) Same mechanism as PR but targets _outerLayout (parent container) instead of page view ✅ PASS ShellItemRenderer.cs Less coupling; no handler introspection
2 try-fix (claude-sonnet-4.6) Walk page view tree, clear stale bottom padding on IHandleWindowInsets views, RequestLayout() — avoids RequestApplyInsets entirely ✅ PASS ShellItemRenderer.cs More invasive; modifies padding directly
3 try-fix (gpt-5.3-codex) LayoutChange listener on _bottomView, fire RequestApplyInsets when height 0→non-zero ❌ FAIL ShellItemRenderer.cs Timing issue — listener fires before layout settles
4 try-fix (gpt-5.4) ViewCompat.DispatchApplyWindowInsets(platformView, cachedRootInsets) via PostDelayed() ✅ PASS ShellItemRenderer.cs Replays cached insets; more complex API usage
5 try-fix (claude-opus-4.6, cross-poll) ViewTreeObserver.AddOnPreDrawListener — fires RequestApplyInsets post-layout, pre-draw ✅ PASS ShellItemRenderer.cs More deterministic timing; requires nested class

Cross-Pollination

Model Round New Ideas? Details
claude-opus-4.6 2 Yes ViewTreeObserver.OnPreDrawListener → ran as Attempt 5 ✅ PASS
claude-sonnet-4.6 2 Yes setOnApplyWindowInsetsListener wrapper that subtracts TabBar height from bottom inset
gpt-5.3-codex 2 Yes Explicit bottom margin/padding = tabBar.measuredHeight
gpt-5.4 2 Yes Fragment/Navigation lifecycle callback hook
claude-sonnet-4.6 3 Yes Synchronous subtraction: paddingBottom - tabBarMeasuredHeight in-line (no Post)

Exhausted: Yes — 5 attempts run, 4 pass, meaningful coverage of the design space achieved; additional ideas are variations on explored themes

Selection

Selected Fix: PR #34324's fix

Comparison Table:

Criterion PR Fix Attempt 1 (_outerLayout) Attempt 2 (tree walk) Attempt 5 (OnPreDraw)
Test passes ✅ ✅ ✅ ✅
Lines added 16 15 35 29
Coupling Medium (reaches into page handler) Low (uses own view) High (mutates padding directly) Medium (reaches into page handler)
Simplicity ✅ Highest ✅ High ❌ Complex tree walk Medium (nested class)
Android idiom Standard RequestApplyInsets Standard Non-standard manual padding Correct but unusual
Risk of regression Low Low Medium (directly modifies padding) Low

Reason: The PR's fix is the simplest correct solution. It uses the standard Android pattern (ViewCompat.RequestApplyInsets) at the most semantically meaningful target (the displayed page's platform view), with appropriate guards (wasGone && showTabs, IsAttachedToWindow, posted after layout). Attempt 1 is slightly cleaner but functionally equivalent. The PR fix directly expresses the intent: "the displayed page needs fresh insets". No independent fix is simpler or more correct.

📋 Report — Final Recommendation

✅ Final Recommendation: APPROVE

Phase Status

Phase Status Notes
Pre-Flight ✅ COMPLETE Issue #33703 — Android regression since .NET 10 RC2
Gate ✅ PASSED Android — test FAIL without fix, PASS with fix
Try-Fix ✅ COMPLETE 5 attempts: 4 PASS, 1 FAIL
Report ✅ COMPLETE

Summary

PR #34324 fixes an Android-specific regression where an empty space appears above the TabBar after navigating back to a page whose TabBar was hidden during navigation. The fix is well-targeted, minimal, and has been validated by Gate testing. Four independent fix approaches were discovered during exploration, and the PR's fix was selected as the simplest and most idiomatic.

Selected Fix: PR — PR's fix was best

Root Cause

When Shell.SetTabBarIsVisible(false) is used on a detail page, Android sets the TabBar (_bottomView) to ViewStates.Gone, allowing the page content to expand to full-screen height. Safe-area insets are recalculated correctly at that point. When navigating back and the TabBar transitions from Gone to Visible, Android does not automatically re-dispatch window insets to child views. The previously calculated bottom padding (sized for a full-screen page) remains unchanged, producing empty space between the page content and the TabBar. This is a regression from .NET MAUI 9.0.90 SR9 and affects Android 13+.

Fix Quality

The fix in ShellItemRenderer.UpdateTabBarVisibility() is clean and well-reasoned:

Strengths:

  • ✅ Minimal change — 16 lines added to a single file; no new classes or abstractions
  • ✅ Correctly scoped — guarded by wasGone && showTabs (only fires on the relevant transition, not on every visibility update)
  • ✅ Safe — platformView.IsAttachedToWindow check inside the Post() callback prevents calls after the view is detached
  • ✅ Idiomatic — ViewCompat.RequestApplyInsets is the standard Android API for this; Post() is the established pattern for deferring to after the layout pass
  • ✅ Well commented — the comment clearly explains why the deferred call is necessary
  • ✅ Test coverage — screenshot UI test TabBarShouldNotHaveEmptySpaceAfterNavigatingBack directly validates the visual regression; test is Android-only (annotated #if ANDROID) with a note explaining why

Minor observations (non-blocking):

  • The approach reaches into DisplayedPage.Handler for PlatformView via a pattern match — slightly tighter coupling than targeting _outerLayout (Attempt 1), but this makes the intent clearer: the displayed page needs fresh insets
  • The snapshot file for the UI test is committed — consistent with the project's screenshot testing pattern

Try-Fix comparison:

Fix Lines Simplicity Risk
PR fix 16 ✅ Highest Low
Attempt 1 (_outerLayout) 15 ✅ High Low
Attempt 2 (tree walk) 35 ❌ Complex Medium
Attempt 4 (DispatchApplyWindowInsets) 20 Medium Low
Attempt 5 (OnPreDrawListener) 29 Medium Low

The PR's fix and Attempt 1 are essentially equivalent in quality. The PR's fix more precisely targets the displayed page's view (the view that actually has stale padding), making the intent self-documenting.

@MauiBot MauiBot added s/agent-approved AI agent recommends approval - PR fix is correct and optimal and removed s/agent-changes-requested AI agent recommends changes - found a better alternative or issues labels Apr 6, 2026
@kubaflo kubaflo changed the base branch from main to inflight/current April 6, 2026 11:51
@kubaflo kubaflo merged commit 747d375 into dotnet:inflight/current Apr 6, 2026
3 of 13 checks passed
PureWeen pushed a commit that referenced this pull request Apr 8, 2026
@praveenkumarkarunanithi @PureWeen
[Android] Fix empty space above TabBar after navigating back when Tab…
7d9f789 
…Bar visibility is toggled (#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes #33703 
Fixes #34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
devanathan-vaithiyanathan pushed a commit to devanathan-vaithiyanathan/maui that referenced this pull request Apr 9, 2026
@praveenkumarkarunanithi @devanathan-vaithiyanathan
[Android] Fix empty space above TabBar after navigating back when Tab…
acb4b02 
…Bar visibility is toggled (dotnet#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes dotnet#33703 
Fixes dotnet#34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
PureWeen pushed a commit that referenced this pull request Apr 14, 2026
@praveenkumarkarunanithi @PureWeen
[Android] Fix empty space above TabBar after navigating back when Tab…
a5f7986 
…Bar visibility is toggled (#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes #33703 
Fixes #34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
@PureWeen PureWeen mentioned this pull request Apr 14, 2026
Merged
@github-actions github-actions Bot mentioned this pull request Apr 15, 2026
Merged
devanathan-vaithiyanathan pushed a commit to Tamilarasan-Paranthaman/maui that referenced this pull request Apr 21, 2026
@praveenkumarkarunanithi @devanathan-vaithiyanathan
[Android] Fix empty space above TabBar after navigating back when Tab…
948a953 
…Bar visibility is toggled (dotnet#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes dotnet#33703 
Fixes dotnet#34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
@github-actions github-actions Bot mentioned this pull request Apr 21, 2026
Open
Ahamed-Ali pushed a commit that referenced this pull request Apr 22, 2026
@praveenkumarkarunanithi @Ahamed-Ali
[Android] Fix empty space above TabBar after navigating back when Tab…
4ec7c9a 
…Bar visibility is toggled (#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes #33703 
Fixes #34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
PureWeen pushed a commit that referenced this pull request Apr 22, 2026
@praveenkumarkarunanithi @PureWeen
[Android] Fix empty space above TabBar after navigating back when Tab…
732965c 
…Bar visibility is toggled (#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes #33703 
Fixes #34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
@github-actions github-actions Bot mentioned this pull request Apr 28, 2026
Open
4 tasks
PureWeen pushed a commit that referenced this pull request Apr 28, 2026
@praveenkumarkarunanithi @PureWeen
[Android] Fix empty space above TabBar after navigating back when Tab…
42ffe22 
…Bar visibility is toggled (#34324)

<!-- Please let the below note in for people that find this PR -->
   > [!NOTE]
   > Are you waiting for the changes in this PR to be merged?
> It would be very helpful if you could [test the resulting
artifacts](https://github.com/dotnet/maui/wiki/Testing-PR-Builds) from
this PR and let us know in a comment if this change resolves your issue.
  Thank you!

### Root Cause
When `Shell.TabBarIsVisible` is set to `false`, Android hides the TabBar
by setting its visibility to Gone. As a result, the page content expands
to occupy the full screen, including the area previously used by the
TabBar. At this point, the safe area padding is calculated correctly
based on the full screen height.
When navigating back and the TabBar becomes visible again, Android
reduces the height of the page content to accommodate the TabBar.
However, Android does not automatically re-apply window insets when a
sibling view changes from Gone to Visible. Because of this, the
previously calculated bottom padding (based on the full screen height)
remains unchanged, leaving an empty space between the page content and
the TabBar.
 
### Description of Change
When the TabBar transitions from Gone to Visible, the fix explicitly
requests Android to re-apply window insets for the currently displayed
page.
The request is posted to run after the layout pass completes, ensuring
the page size has been updated before safe area padding is recalculated.
An additional check ensures that the page is still attached to the
window before requesting insets to avoid unnecessary calls.
By forcing Android to re-apply window insets after the layout update,
the safe area padding is recalculated using the updated page height,
eliminating the empty space above the TabBar. The fix is scoped to run
only when the TabBar transitions from hidden to visible.

### Issues Fixed
Fixes #33703 
Fixes #34256 
 
Tested the behaviour in the following platforms
- [x] Android
- [x] Windows
- [x] iOS
- [x] Mac

### Note
The UI test is added for Android only as this issue is specific to
Android — the empty space above the TabBar after navigating back only
reproduces on Android.

### Output Video
Before Issue Fix | After Issue Fix |
|----------|----------|
|<video width="40" height="60" alt="Before Fix"
src="https://github.com/user-attachments/assets/f89ff481-59b2-45b4-9827-dabb7991d905">|<video
width="50" height="40" alt="After Fix"
src="https://github.com/user-attachments/assets/ee56ec91-5cd5-4d07-bd0e-6d99d2055acf">|

---------
PureWeen added a commit that referenced this pull request Apr 29, 2026
@PureWeen
April 14th, Candidate (#34885)
4c231e9 
## Blazor
- Fix: Filter precompressed RCL assets from MAUI Blazor Hybrid APKs by
@mattleibow in #33917
  <details>
  <summary>🔧 Fixes</summary>

- [.NET MAUI Blazor Hybrid App should not precompress
assets](#33773)
  </details>

- [Windows] Fix for Runtime error when closing external window with WPF
Webview Control by @BagavathiPerumal in
#34006
  <details>
  <summary>🔧 Fixes</summary>

- [Runtime error when closing external window with WPF Webview
Control](#32944)
  </details>

## Button
- [Android] ImageButton CornerRadius not being applied - fix by @kubaflo
in #30074
  <details>
  <summary>🔧 Fixes</summary>

- [ImageButton CornerRadius not being applied on
Android](#23854)
  </details>

- Fix Disabled visual state ignored when Button has locally-set
BackgroundColor/TextColor by @Dhivya-SF4094 in
#34444
  <details>
  <summary>🔧 Fixes</summary>

- [[regression/9.0] VisualState "Disabled" is not properly applied for
Button with custom
appearance](#34363)
  </details>

## CollectionView
- Fix CollectionView grid spacing updates for first row and column by
@KarthikRajaKalaimani in #34527
  <details>
  <summary>🔧 Fixes</summary>

- [[MAUI] I2_Vertical grid for horizontal Item Spacing and Vertical Item
Spacing - horizontally updating the spacing only applies to the second
column](#34257)
  </details>

- Fix CollectionView record struct selection on Windows by
@jeremy-visionaid in #33488

- [Android] Ensure disconnected ItemsViewHandler doesn't hold onto the
items source by @filipnavara in
#24610
  <details>
  <summary>🔧 Fixes</summary>

- [Crash on NullReferenceException with measurement cells in
CollectionView](#24304)
  </details>

- [Windows] Fixed VisualState Setters not working properly for
CollectionView by @Dhivya-SF4094 in
#27230
  <details>
  <summary>🔧 Fixes</summary>

- [VisualState Setters not working properly on Windows for a
CollectionView](#27086)
- [[regression/8.0.3] [Windows][CollectionView]Label Disappear when set
Style in
ContentPage.Resources](#19209)
- [[Windows] Label style defined as ContentPage Resource doesn't
propagate to
CollectionView](#18701)
  </details>

- [Windows] Fixed Margin doesn't work inside CollectionView EmptyView by
@Dhivya-SF4094 in #29897
  <details>
  <summary>🔧 Fixes</summary>

- [Margin doesn't work inside CollectionView
EmptyView](#8494)
  </details>

- [Android, Windows] Fix CarouselView PreviousPosition/PreviousItem
incorrect during animated ScrollTo() by @praveenkumarkarunanithi in
#34570
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] CurrentItemChangedEventArgs.PreviousItem and
PositionChangedEventArgs.PreviousPosition Not Updating Correctly When
Using ScrollTo or Setting
Position](#29544)
  </details>

- [iOS] CarouselView2: Update internal scroll indicators for
compositional layout by @SubhikshaSf4851 in
#33639
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] Horizontal Scroll Bar Not Visible on CarouselView
(CV2)](#29390)
  </details>

- [CarouselViewHandler2] Fir fox CurrentItem does not work when
ItemSpacing is set by @SyedAbdulAzeemSF4852 in
#32135
  <details>
  <summary>🔧 Fixes</summary>

- [[CarouselViewHandler2] CurrentItem does not work when ItemSpacing is
set](#32048)
  </details>

- [iOS] Fix for Incorrect Scroll in Loop Mode When CurrentItem Is Not
Found in ItemsSource by @SyedAbdulAzeemSF4852 in
#32141
  <details>
  <summary>🔧 Fixes</summary>

- [[Android & iOS] Setting an invalid CurrentItem causes scroll to last
item in looped
CarouselView](#32139)
  </details>

- [Android] IndicatorView: Add TalkBack accessibility descriptions for
indicators by @praveenkumarkarunanithi in
#31775
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] IndicatorView does not convey correct accessibility
information](#31446)
  </details>

- [iOS, macOS] Fixed CollectionView KeepLastItemInView Not Updating
Correctly When Items Are Added Dynamically by @NanthiniMahalingam in
#32191
  <details>
  <summary>🔧 Fixes</summary>

- [[.NET10] I9 - Scroll_Position - "KeepLastItemInView" does not keep
the last item at the end of the displayed list when adding new
items.](#31825)
  </details>

- [Windows, Android] Resolved issue with dynamic Header/Footer
reassignment in CollectionView. by @prakashKannanSf3972 in
#28403
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows, Android] Toggling Header/Footer in CollectionView
Dynamically is not working](#27959)
- [CollectionView HeaderTemplate and FooterTemplate are not displayed
when ItemsSource is initially set to
null](#28337)
- [[Android] Header and Footer Not Visible in CollectionView When
EmptyView is Selected
First](#28351)
  </details>

- [Android] Fix CollectionView inside disabled RefreshView blocks scroll
by @Vignesh-SF3580 in #34702
  <details>
  <summary>🔧 Fixes</summary>

- [C6-The C6 page cannot scroll on Windows and Android
platforms.](#34666)
  </details>

- [Android] CollectionView: Fix SelectedItem visual state not applying
when re-selecting same item by @KarthikRajaKalaimani in
#31591
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView - SelectedItem visual state manager not
working](#20062)
  </details>

- [Windows] Fixed CollectionView.EmptyView can not be removed by setting
it to Null by @Dhivya-SF4094 in
#29487
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows] CollectionView.EmptyView can not be removed by setting it
to Null](#18657)
- [[Windows] EmptyViewTemplate Not Working in
CarouselView](#29463)
- [EmptyViewTemplate does not do
anything](#18551)
- [[MAUI] I5_EmptyView - The data template selector cannot display the
correct string.](#23330)
  </details>

- [iOS] Support for IsSwipeEnabled on CarouselView2 by @kubaflo in
#29996
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] IsSwipeEnabled Not Working on CarouselView
(CV2)](#29391)
  </details>

- [iOS, MacOS] Fixed FlowDirection not working on Header/Footer in
CollectionView by @Dhivya-SF4094 in
#32775
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS, MacOS] FlowDirection not working on Header/Footer in
CollectionView](#32771)
  </details>

- [iOS] CollectionView: Fix drag-and-drop reordering into empty groups
by @SuthiYuvaraj in #34151
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView Drag and Drop Reordering Can't Drop in Empty
Group](#12008)
  </details>

- [Android] CollectionView: Fix drag-and-drop reordering into empty
groups by @SuthiYuvaraj in #31867
  <details>
  <summary>🔧 Fixes</summary>

- [CollectionView Drag and Drop Reordering Can't Drop in Empty
Group](#12008)
  </details>

- [iOS] Fix vertical CarouselView MandatorySingle snapping on iOS by
@Vignesh-SF3580 in #34700
  <details>
  <summary>🔧 Fixes</summary>

- [CarouselView vertical snap points ignored on iOS with
Microsoft.Maui.Controls v10.0.20 (regression from
v9.0.120)](#33308)
  </details>

- [iOS26] Fix CarouselView scrolling to wrong item when navigating to
last item by @Vignesh-SF3580 in
#34013
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS 26] CarouselView does not scroll to the correct last
item](#33770)
  </details>

- Fixed the OnPlatform does not work for header property in Collection
view by @NanthiniMahalingam in #28935
  <details>
  <summary>🔧 Fixes</summary>

- [OnPlatform does not work in Header of
CollectionView](#25124)
  </details>

- [Android] [Candidate branch] Fix
VerifySelectedItemClearsOnNullAssignment,
CollectionViewSelectionShouldClear, SelectedItemVisualIsCleared UI test
failure on Android by @KarthikRajaKalaimani in
#34928

## DateTimePicker
- [iOS] Fix for DatePicker FlowDirection Not Working on iOS by
@SyedAbdulAzeemSF4852 in #30193
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] DatePicker FlowDirection Not Working on
iOS](#30065)
  </details>

## Drawing
- [Shapes] Line: Fix asymmetric Stretch.None path translation when
right/bottom edge overflows by @NirmalKumarYuvaraj in
#34385
  <details>
  <summary>🔧 Fixes</summary>

- [Line coordinates not computed
correctly](#11404)
- [Lines not drawing
correctly](#26961)
  </details>

- [Android] Fixed GraphicsView drawable is visible outside the canvas by
@NirmalKumarYuvaraj in #28353
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] GraphicsView， The drawn image can also be visible outside
the canvas](#20834)
  </details>

- Fixed Custom Drawable does not support binding by @NirmalKumarYuvaraj
in #29442
  <details>
  <summary>🔧 Fixes</summary>

- [Custom IDrawable control does not databind to a model property when
used inside a CollectionView
ItemTemplate](#20991)
  </details>

- Added a support for GradientBrushes on Shape.Stroke by @kubaflo in
#22208
  <details>
  <summary>🔧 Fixes</summary>

- [GradientBrushes are not supported on
Shape.Stroke](#21983)
  </details>

## Editor
- Fixed Editor HorizontalTextAlignment does not update at run time by
@NirmalKumarYuvaraj in #25129
  <details>
  <summary>🔧 Fixes</summary>

- [Editor HorizontalTextAlignment Does not
Works.](#10987)
- [[iOS/MacOs] Right-To-Left (RTL) alignment is not applied to Editor
placeholder](#30052)
  </details>

- [Windows] Fixed Entry Editor placeholder Text CharacterSpacing by
@SubhikshaSf4851 in #30324
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows] CharacterSpacing not applied to Placeholder text in Entry
and Editor controls](#30071)
  </details>

## Entry
- [Windows] Fix fo setting an Entry's Keyboard to Date causes it to be
interpreted as a password input by @SyedAbdulAzeemSF4852 in
#29344
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows] Entry Keyboad-Type "Date" results in
Password-Entry](#28975)
  </details>

- [Android] Exception thrown when give more than 5000 characters to the
Text property of Entry. by @KarthikRajaKalaimani in
#30242
  <details>
  <summary>🔧 Fixes</summary>

- [Android crash when Entry has >5000
characters](#30144)
  </details>

## Essentials
- Bump MonoApiToolsMSBuildTasksPackageVersion to 0.5.0 and ship
Essentials.AI public APIs by @mattleibow via @Copilot in
#34574

- [Mac] DeviceDisplay.KeepScreenOn not being respected on Mac OS by
@HarishwaranVijayakumar in #32708
  <details>
  <summary>🔧 Fixes</summary>

- [[Mac Catalyst] DeviceDisplay.KeepScreenOn not being respected on Mac
OS](#26059)
  </details>

## Flyoutpage
- [Windows] FlyoutPage: update CollapseStyle at runtime by
@devanathan-vaithiyanathan in #29927
  <details>
  <summary>🔧 Fixes</summary>

- [Flyout Page SetCollapseStyle doesn't have any
change](#18200)
  </details>

## Gestures
- [Android] Fix for TapGestureRecognizer doesn't fire by
@HarishwaranVijayakumar in #34497
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] TapGestureRecognizer doesn't
fire](#5825)
  </details>

## Image
- [Android] Fix Share.RequestAsync SecurityException on Android 10+
caused by missing ClipData by @HarishwaranVijayakumar in
#34417
  <details>
  <summary>🔧 Fixes</summary>

- [[Bug] Share.RequestAsync throws java.lang.SecurityException
(uid=1000) on Android 10+ due to missing
intent.ClipData](#34370)
  </details>

- [Windows]Fixed the MauiImage with logical name containing path issue
by @sheiksyedm in #32864
  <details>
  <summary>🔧 Fixes</summary>

- [MauiImage with LogicalName containing path - is not working on
Windows](#32356)
  </details>

- [Android, Windows & iOS] Fix Downsize/ScaleImage to maintain aspect
ratio and prevent upscaling by @SyedAbdulAzeemSF4852 in
#30808
  <details>
  <summary>🔧 Fixes</summary>

- [[Android & Windows] In GraphicsView, the aspect ratio is not
maintained when Downsize is called with both maxWidth and
maxHeight](#30803)
  </details>

## Label
- [iOS , macOS] Fixed Label text cropping when a width request is
specified on the label inside a VerticalStackLayout with specified width
request by @NanthiniMahalingam in
#29166
  <details>
  <summary>🔧 Fixes</summary>

- [Label text gets cropped when a width request is specified on the
label inside a
VerticalStackLayout](#28660)
- [[iOS] Label with a fixed WidthRequest has wrong
height](#26644)
  </details>

- [Android] Fix Label word wrapping clips text depending on alignment
and layout options by @Dhivya-SF4094 in
#34533
  <details>
  <summary>🔧 Fixes</summary>

- [Bug: Android Label word wrapping clips text depending on alignment
and layout options](#34459)
  </details>

- LineHeight and decorations for HTML Label - fix by @kubaflo in
#31202
  <details>
  <summary>🔧 Fixes</summary>

- [LineHeight with HTML Label not
working](#22193)
  - [lineheight is broken ](#22197)
  </details>

- [iOS] Fix Label with TailTruncation not rendering after
empty-to-non-empty text transition by @kubaflo in
#34812
  <details>
  <summary>🔧 Fixes</summary>

- [Label with LineBreakMode="TailTruncation" does not render text if
initial Text is null or empty on first render
(iOS)](#34591)
  </details>

## Layout
- [Android] Fix overflowing children clipped when parent Opacity < 1 by
@SyedAbdulAzeemSF4852 in #34565
  <details>
  <summary>🔧 Fixes</summary>

- [Maui Android parent view inappropriately creates clipping mask when
its opacity is less than 1, cropping out
children](#22038)
  </details>

- Fixed the FlexLayout reverse issue with the AlignContent by
@Ahamed-Ali in #32134
  <details>
  <summary>🔧 Fixes</summary>

- [FlexLayout alignment issue when Wrap is set to Reverse and
AlignContent is set to SpaceAround, SpaceBetween or
SpaceEvenly](#31565)
  </details>

- [iOS/Mac] Fixed BoxView in AbsoluteLayout did not return to its
default AutoSize for Height and Width after reset by @Dhivya-SF4094 in
#31648
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS, Catalyst] BoxView in AbsoluteLayout does not return to default
AutoSize for Height/Width after
reset](#31496)
  </details>

## Map
- [Windows] Implement WinUI 3 MapControl handler using Azure Maps by
@jfversluis in #34138

## Modal
- [Android] PopToRootAsync for modal pages - improvements by @kubaflo in
#26851
  <details>
  <summary>🔧 Fixes</summary>

- [Shell PopToRootAsync doesn't happen instantly - previous pages flash
quickly. Only happens in NET
9](#26846)
  </details>

- [Android] Fix HideSoftInputOnTapped doesn't work on Modal Pages by
@HarishwaranVijayakumar in #34770
  <details>
  <summary>🔧 Fixes</summary>

- [HideSoftInputOnTapped doesn't work on Modal
Pages](#34730)
  </details>

## Navigation
- [iOS] Alert popup may be displayed on wrong window when modal page
navigation is in progress - fix by @kubaflo in
#31016
  <details>
  <summary>🔧 Fixes</summary>

- [Alert popup may be displayed on wrong window when modal page
navigation is in progress on
iOS/MacOS](#30970)
  </details>

- [Android] Page: Fix OnNavigatedTo called twice when NavigationPage is
FlyoutPage Detail by @KarthikRajaKalaimani in
#31931
  <details>
  <summary>🔧 Fixes</summary>

- [NavigationPage and FlyoutPage both call OnNavigatedTo, so it is
called twice](#23902)
  </details>

## Picker
- Fixed the Picker didn't dismiss it when tapping outside on iOS and
MacCatalyst platform. by @KarthikRajaKalaimani in
#30067
  <details>
  <summary>🔧 Fixes</summary>

- [[regression/8.0.3] iOS Picker dismiss does not work when clicking
outside of the Picker](#19168)
  </details>

- [Windows] Fixed Picker items width wont resize back by
@SubhikshaSf4851 in #33042
  <details>
  <summary>🔧 Fixes</summary>

- [Picker items width won't resize back when its container window gets
resized down.](#32984)
  </details>

## RadioButton
- Fix TalkBack not correctly narrating RadioButtons with Content by
@SubhikshaSf4851 in #34521
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] TalkBack does not correctly narrate RadioButtons with
Content](#34322)
  </details>

## SafeArea
- [Android] Fix SafeAreaShouldWorkOnAllShellTabs test failure on API 36
by @praveenkumarkarunanithi in #34239

## ScrollView
- [iOS] Preserve ScrollView offsets when Orientation changes to Neither
by @Vignesh-SF3580 in #34672
  <details>
  <summary>🔧 Fixes</summary>

- [Incorrect implementation of
ScrollView.Orientation](#34583)
  </details>

## Searchbar
- [Android] Fix SearchBar text bleeding between instances after
navigation by @SyedAbdulAzeemSF4852 in
#34703
  <details>
  <summary>🔧 Fixes</summary>

- [MAUI Android: SearchBar copies content from one to the
other](#20348)
  </details>

- Fixed SearchBar CursorPosition and SelectionLength not updating when
typing by @Dhivya-SF4094 in #34347
  <details>
  <summary>🔧 Fixes</summary>

- [SearchBar - CursorPosition and SelectionLength are not updated when
the user types](#30779)
  </details>

## SearchBar
- [Windows] Fixed SearchHandler issues by @Tamilarasan-Paranthaman in
#29520
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows] SearchHandler APIs are not functioning
properly](#29493)
  </details>

## Shell
- [iOS, Mac] Fix for Background set to Transparent doesn't have the same
behavior as BackgroundColor Transparent by @HarishwaranVijayakumar in
#32245
  <details>
  <summary>🔧 Fixes</summary>

- [Background set to Transparent doesn't have the same behavior as
BackgroundColor =
Transparent](#22769)
  </details>

- [iOS] Fix App crash with NullReferenceException in
ShellSectionRenderer by @devanathan-vaithiyanathan in
#32109
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS] App crash with NullReferenceException in
ShellSectionRenderer](#31961)
  </details>

- [Android] Fixed back button icon selection logic in
ShellToolbarTracker by @kubaflo in
#32080
  <details>
  <summary>🔧 Fixes</summary>

- [IconOverride in Shell.BackButtonBehavior does not
work.](#32050)
  </details>

- Fix TabBarIsVisible Not Updating Dynamically When Set on ShellContent
by @Vignesh-SF3580 in #33090
  <details>
  <summary>🔧 Fixes</summary>

- [Shell.TabBarIsVisible is not updated dynamically at
runtime](#32994)
  </details>

- [iOS, macOS] Shell: Fix RTL flow direction for flyout, menu cells, tab
bar, and Locked flyout position by @NanthiniMahalingam in
#32701
  <details>
  <summary>🔧 Fixes</summary>

- [[iOS, Mac Catalyst] Shell Flyout and Content Do Not Fully Support
RightToLeft (RTL)](#32419)
  </details>

- [IOS] Inconsistent Resize Behavior for Header/Footer - fix by @kubaflo
in #28713
  <details>
  <summary>🔧 Fixes</summary>

- [[IOS, Mac] Inconsistent Resize Behavior for
Header/Footer](#26397)
- [Enable Shell Flyout Header/Footer resize tests on
iOS/Catalyst](#33501)
  </details>

- [Android] Fix for SearchHandler retaining previous page SearchView
data in pages within Shell sections by @BagavathiPerumal in
#29545
  <details>
  <summary>🔧 Fixes</summary>

- [[Shell][Android] The truth is out there...but not on top tab search
handlers](#8716)
  </details>

- [Android] Fix empty space above TabBar after navigating back when
TabBar visibility is toggled by @praveenkumarkarunanithi in
#34324
  <details>
  <summary>🔧 Fixes</summary>

- [Empty space appears above TabBar after navigating back when TabBar
visibility is toggled](#33703)
- [Grid with SafeAreaEdges=Container has incorrect size when tab bar
appears](#34256)
  </details>

## SwipeView
- [Android] SwipeView: Use MeasureSpecMode.Exactly for SwipeItem layout
to fix text visibility by @Ahamed-Ali in
#27399
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] Right SwipeView items are not visible in the
SwipeView.](#27367)
  </details>

- [Android] Prevent the tap that closes an open SwipeView from being
propagated to children by @sjordanGSS in
#24275
  <details>
  <summary>🔧 Fixes</summary>

- [Tapping to close a SwipeView will activate TapGestureRecognizers on
.Content](#23921)
  </details>

## Switch
- [iOS & Mac] Fix for SearchHandler retains previous page state when
switching top tabs by @BagavathiPerumal in
#34735
  <details>
  <summary>🔧 Fixes</summary>

- [[Shell] [iOS & Mac] SearchHandler retains previous page state when
switching top tabs](#34693)
  </details>

## TabbedPage
- [Android] Fixed NullReferenceException in app with TabBar after
returning from minimized state by @NirmalKumarYuvaraj in
#34779
  <details>
  <summary>🔧 Fixes</summary>

- [NullReferenceException in app with TabBar after returning from
minimized state](#34720)
  </details>

## Titlebar
- Fixed BindingContext of the Window TitleBar is not being passed on to
its child content. by @NirmalKumarYuvaraj in
#30080
  <details>
  <summary>🔧 Fixes</summary>

- [The BindingContext of the Window TitleBar is not being passed on to
its child content.](#24831)
  </details>

- [Windows/Mac] Fix RTL FlowDirection causes overlap with native window
control buttons in TitleBar by @devanathan-vaithiyanathan in
#30400
  <details>
  <summary>🔧 Fixes</summary>

- [[Windows, Mac] RTL FlowDirection causes overlap with native window
control buttons in
TitleBar](#30399)
  </details>

## WebView
- [Windows] Fix WebView background color not being applied by
@SubhikshaSf4851 in #34599
  <details>
  <summary>🔧 Fixes</summary>

- [WebView background color has changed after update, can't
override.](#34518)
  </details>

- [Android] Fix for WebView/HybridWebView briefly flashes full screen
before layout completes by @praveenkumarkarunanithi in
#33207
  <details>
  <summary>🔧 Fixes</summary>

- [[Android] HybridWebView briefly resizes to full screen when page is
opened before snapping back to correct
size](#31475)
  </details>

## Xaml
- Improved style inheritance by @kubaflo in
#31317
  <details>
  <summary>🔧 Fixes</summary>

- [Styles based on a style that is based on another style that uses
AppThemeBinding do not inherit properties
correctly.](#31280)
  </details>

- Fix for VisualStateManager Setter.TargetName failing when
ControlTemplate is applied by @BagavathiPerumal in
#33208
  <details>
  <summary>🔧 Fixes</summary>

- [Setter.TargetName + ControlTemplate
crash](#26977)
  </details>


<details>
<summary>🧪 Testing (4)</summary>

- [Testing] Additional Feature Matrix Event Test Cases for Slider and
ScrollView by @nivetha-nagalingam in
#34352
- [Testing] Fixed Build error on inflight/ candidate PR 34885 by
@NafeelaNazhir in #34891
- [Testing] Fixed UI test image failure in PR 34885 - [13/4/2026] by
@NafeelaNazhir in #34933
- Fixed test failure - CursorPositionUpdatesWhenSearchBarGainsFocus by
@Dhivya-SF4094 in #34938

</details>

<details>
<summary>📦 Other (3)</summary>

- Fix Loaded event not called for MAUI View added to native View by
@NirmalKumarYuvaraj in #34345
  <details>
  <summary>🔧 Fixes</summary>

- [Loaded event not called for MAUI View added to native
View](#34310)
  </details>
- Add public IAlertManager and IAlertManagerSubscription interfaces by
@Redth in #34228
  <details>
  <summary>🔧 Fixes</summary>

- [Alert/Dialog system (`DisplayAlert`, `DisplayActionSheet`,
`DisplayPromptAsync`) needs a public extensibility
point](#34104)
  </details>
- Fix crash when displaying alerts on unloaded pages by @kubaflo in
#33288

</details>

<details>
<summary>📝 Issue References</summary>

Fixes #5825, Fixes #8494, Fixes #8716, Fixes #10987, Fixes #11404, Fixes
#12008, Fixes #18200, Fixes #18551, Fixes #18657, Fixes #18701, Fixes
#19168, Fixes #19209, Fixes #20062, Fixes #20348, Fixes #20834, Fixes
#20991, Fixes #21983, Fixes #22038, Fixes #22193, Fixes #22197, Fixes
#22769, Fixes #23330, Fixes #23854, Fixes #23902, Fixes #23921, Fixes
#24304, Fixes #24831, Fixes #25124, Fixes #26059, Fixes #26397, Fixes
#26644, Fixes #26846, Fixes #26961, Fixes #26977, Fixes #27086, Fixes
#27367, Fixes #27959, Fixes #28337, Fixes #28351, Fixes #28660, Fixes
#28975, Fixes #29390, Fixes #29391, Fixes #29463, Fixes #29493, Fixes
#29544, Fixes #30052, Fixes #30065, Fixes #30071, Fixes #30144, Fixes
#30399, Fixes #30779, Fixes #30803, Fixes #30970, Fixes #31280, Fixes
#31446, Fixes #31475, Fixes #31496, Fixes #31565, Fixes #31825, Fixes
#31961, Fixes #32048, Fixes #32050, Fixes #32139, Fixes #32356, Fixes
#32419, Fixes #32771, Fixes #32944, Fixes #32984, Fixes #32994, Fixes
#33308, Fixes #33501, Fixes #33703, Fixes #33770, Fixes #33773, Fixes
#34104, Fixes #34256, Fixes #34257, Fixes #34310, Fixes #34322, Fixes
#34363, Fixes #34370, Fixes #34459, Fixes #34518, Fixes #34583, Fixes
#34591, Fixes #34666, Fixes #34693, Fixes #34720, Fixes #34730

</details>

**Full Changelog**:
main...inflight/candidate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot Copilot left review comments

@kubaflo kubaflo kubaflo approved these changes

Assignees

No one assigned

Labels

area-controls-shell Shell Navigation, Routes, Tabs, Flyout community ✨ Community Contribution partner/syncfusion Issues / PR's with Syncfusion collaboration platform/android s/agent-approved AI agent recommends approval - PR fix is correct and optimal s/agent-fix-pr-picked AI could not beat the PR fix - PR is the best among all candidates s/agent-reviewed PR was reviewed by AI agent workflow (full 4-phase review)

Projects

None yet

Milestone

No milestone

7 participants

@praveenkumarkarunanithi @sheiksyedm @MauiBot @kubaflo @karthikraja-arumugam @jfversluis