[Android] CollectionView: Fix SelectedItem visual state not applying when re-selecting same item

[KarthikRajaKalaimani]

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!

Issue Details:

The selected item background color is not applied in Android platform.

Root Cause:

On Android, UpdateMauiSelection sets ItemsView.SelectedItem to the newly tapped item. When the ItemsSource contains duplicate values (e.g., all string "a" items), assigning the new item doesn't change SelectedItem because the value is equal to the previous one. As a result, VisualStateManager.GoToState() is never called on the new item's TemplatedItemViewHolder, so the Selected visual state is never applied.

Description of Change:

In SelectableItemsViewAdapter.UpdateMauiSelection (Android), when SelectionMode.Single is in use:

• Before setting SelectedItem, the previous value is captured.
• After setting, if the previous and new values are equal (duplicate item), the fix manually forces the visual state update:
  i) Calls ClearPlatformSelection() to deselect all ViewHolders.
  ii) Sets IsSelected = true on the ViewHolder at the tapped position, which triggers OnSelectedChanged() → VisualStateManager.GoToState("Selected").

This ensures the visual state is refreshed even when SelectedItem doesn't change.

Tested the behavior in the following platforms.

• Android
• Windows
• iOS
• Mac

Reference:

N/A

Issues Fixed:

Fixes #20062

Screenshots

Before	After
Screen.Recording.2025-09-12.at.5.57.06.PM.mov	Screen.Recording.2025-09-12.at.6.06.31.PM.mov

[dotnet-policy-service]

Hey there @@KarthikRajaKalaimani! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

/azp run MAUI-UITests-public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jsuarezruiz]

Test failing on iOS:

Could you review it?

[KarthikRajaKalaimani]

Test failing on iOS: Could you review it?

I have updated the snapshot for iOS platform.

[Copilot]

Pull Request Overview

This PR fixes an issue with CollectionView's VisualStateManager not applying selected item visual states properly on Android when items have duplicate values. The core problem was that when selecting an item with the same value as the previously selected item, the selection change wasn't being recognized, preventing the visual state from updating.

• Adds logic to detect when the same item value is selected and force a visual state update
• Implements test coverage for the CollectionView selection visual state behavior
• Clears platform selection state and re-applies selection to trigger VisualStateManager updates

Reviewed Changes

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

File	Description
src/Controls/src/Core/Handlers/Items/Android/Adapters/SelectableItemsViewAdapter.cs	Adds logic to handle duplicate item selection by clearing and re-applying platform selection state
src/Controls/tests/TestCases.HostApp/Issues/Issue20062.cs	Creates UI test page with CollectionView containing duplicate items and VisualStateManager for selection states
src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue20062.cs	Implements automated test to verify CollectionView selection visual state changes work correctly

[h0lg]

Looks promising! Any chance this gets fixed soon?

[kubaflo]

⚠️ Merge Conflict Detected — This PR has merge conflicts with its target branch. Please rebase onto the target branch and resolve the conflicts.

[github-actions]

🚀 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://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.sh | bash -s -- 31591

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/maui/main/eng/scripts/get-maui-pr.ps1) } 31591"

[kubaflo]

🤖 AI Summary

📊 Expand Full Review — 142f41f · Code formatted

---

🔍 Pre-Flight — Context & Validation

---

Issue: #20062 - CollectionView - SelectedItem visual state manager not working
PR: #31591 - CollectionView - SelectedItem visual state manager not working
Platforms Affected: Android (primary bug), iOS also mentioned but fix is Android-only
Files Changed: 1 implementation (Android), 1 HostApp test, 1 Shared test, 3 snapshot images

Key Findings

• Bug: When SelectionMode.Single is used and multiple items have equal values (e.g., all "a"), assigning SelectedItem doesn't trigger a change notification (value equality prevents it), so VisualStateManager.GoToState("Selected") is never called on the new item.
• Fix: In SelectableItemsViewAdapter.UpdateMauiSelection (Android), captures previouslySelectedItem before assignment. If it equals the new item after assignment, manually forces visual state via ClearPlatformSelection() + _currentViewHolders[viewHolderIndex].IsSelected = true.
• The fix is Android-only (in the Items/Android handler path).
• HostApp [Issue] attribute says PlatformAffected.Android but test runs on iOS and Mac too (no TEST_FAILS_ON_IOS / TEST_FAILS_ON_MAC guard).
• iOS reviewer comment: test was failing on iOS — author claims they updated the snapshot (but the iOS fix is unrelated to the PR's code change).
• Potential risk: _currentViewHolders[viewHolderIndex] uses a raw list index; _currentViewHolders contains only currently-visible (bound) ViewHolders. With scrolling/recycling the index may not correspond to a visible item.
• PR has an active merge conflict warning from kubaflo (2026-03-15).
• Prior agent review: labels s/agent-reviewed, s/agent-changes-requested, s/agent-gate-failed, s/agent-fix-pr-picked are present.
• No newline at end of TestCases.Shared.Tests/Tests/Issues/Issue20062.cs.

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #31591	Capture previous SelectedItem; if equal after set, call ClearPlatformSelection() + force IsSelected=true on tapped ViewHolder	⏳ PENDING (Gate)	SelectableItemsViewAdapter.cs	Android only; index-based ViewHolder lookup may be fragile

Result: ✅ COMPLETE

---

🚦 Gate — Test Verification

---

Gate Result: ❌ FAILED

Platform: android
Mode: Full Verification

• Tests FAIL without fix: ❌
• Tests PASS with fix: ✅

---

Details

Run 1 (WITHOUT fix): CollectionViewSelectionChangesVisualState — ✅ PASSED (expected: FAIL)

Run 2 (WITH fix): CollectionViewSelectionChangesVisualState — ✅ PASSED

Root Cause: Test does not reproduce the bug

The test scenario taps FirstItem then ThirdItem. These are distinct Issue20062_Item object instances (different references), so setting ItemsView.SelectedItem from FirstItem_object to ThirdItem_object does fire the property-changed notification, and the VisualStateManager updates correctly — even without the fix.

The fix's conditional code path (previouslySelectedItem == ItemsView.SelectedItem) is only triggered when the same object is re-selected (identical reference). This happens, for example, when:

• All items are the same string literal (e.g., "a" as a raw string, not wrapped in a class), or
• The user taps an already-selected item again.

Since Issue20062_Item does not override Equals, reference equality is used, and tapping a different item (even with the same Name = "a") produces a different object → the existing code path works correctly → the bug is not reproduced by this test.

Recommendation: Update the test to reproduce the actual bug. For example:

• Use a List<string> with duplicate string values (e.g., new List<string> { "a", "a", "a", "a" })
• Or test re-tapping the currently selected item (tap FirstItem twice)

---

🔧 Fix — Analysis & Comparison

---

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #31591	Capture prev SelectedItem; if equal, ClearPlatformSelection() + direct list index lookup	⚠️ BLOCKED (test doesn't repro bug)	SelectableItemsViewAdapter.cs	Index-based lookup is fragile
1	Attempt-1 (claude-opus-4.6-1m)	Same logic but loop _currentViewHolders matching BindingAdapterPosition == adapterPosition instead of direct index	⚠️ BLOCKED	SelectableItemsViewAdapter.cs	Safer VH lookup; test can't verify
2	Attempt-2 (claude-sonnet-4.6)	Proactive update BEFORE setting SelectedItem: always ClearPlatformSelection + loop to find VH by BindingAdapterPosition	⚠️ BLOCKED	SelectableItemsViewAdapter.cs	Eliminates equality check; test can't verify
3	Attempt-3 (gpt-5.3-codex)	Track previous adapter position; use SetValueCore(RaiseOnEqual); position-aware MarkPlatformSelection	⚠️ BLOCKED	SelectableItemsViewAdapter.cs	Avoids value-equality ambiguity; test can't verify
4	Attempt-4 (gemini-3-pro-preview)	Two-part: (1) Fix test—add Equals/GetHashCode to Issue20062_Item so bug actually reproduces; (2) Fix code—iterate _currentViewHolders by BindingAdapterPosition in SelectableClicked, unconditionally set IsSelected	✅ PASS	SelectableItemsViewAdapter.cs + Issue20062.cs	Clean position-driven fix; test fix was the critical unlock

Cross-Pollination

Model	Round	New Ideas?	Details
claude-opus-4.6-1m	2	No	Confirmed Attempt 4 is architecturally best: position-driven, no equality games, no fragile indexing

Exhausted: Yes
Selected Fix: Attempt 4 (gemini-3-pro-preview) — Position-driven visual state update on tap + test fix to reproduce the bug. Clean, robust, and surgically scoped to the tap code path.

---

📋 Report — Final Recommendation

---

⚠️ Final Recommendation: REQUEST CHANGES

Phase Status

Phase	Status	Notes
Pre-Flight	✅ COMPLETE	Issue #20062, Android CollectionView SelectionMode.Single with value-equal items
Gate	❌ FAILED	Test passes without fix — test doesn't reproduce the bug
Try-Fix	✅ COMPLETE	4 attempts; 1 passing (Attempt 4 — gemini)
Report	✅ COMPLETE

Summary

PR #31591 fixes a real, verified bug in Android CollectionView: when SelectionMode.Single is used and items have equal values (e.g., all "a" strings), tapping a different item doesn't update the visual state because BindableProperty suppresses PropertyChanged when the new value equals the current one.

The fix direction is correct, but the PR has two issues that need to be addressed before merging:

1. The test doesn't actually reproduce the bug — items use reference-type objects (Issue20062_Item) without Equals/GetHashCode, so they're never value-equal and the bug never manifests in tests.
2. The code fix uses a fragile direct list index — _currentViewHolders[hasHeader ? adapterPosition - 1 : adapterPosition] assumes a direct mapping between adapter position and list index, which is incorrect since _currentViewHolders is an unordered list of only visible ViewHolders. This can cause IndexOutOfRangeException or update the wrong ViewHolder during scrolling/recycling.

Root Cause

BindableProperty.SetValue skips change notification when the new value equals the current value. When all CollectionView items are value-equal (e.g., same string), selecting any item after the first silently no-ops, leaving VisualStateManager.GoToState("Selected") uncalled for the newly-tapped ViewHolder.

Fix Quality Assessment

PR's code fix — ⚠️ Partially correct, fragile:

var viewHolderIndex = ItemsSource.HasHeader ? adapterPosition - 1 : adapterPosition;
ClearPlatformSelection();
_currentViewHolders[viewHolderIndex].IsSelected = true;

This uses a raw list index into _currentViewHolders. Since _currentViewHolders is populated as ViewHolders are bound and removed as they're recycled, its indices do not map to adapter positions. This can throw IndexOutOfRangeException or select the wrong item.

Attempt 4 fix — ✅ Better (empirically verified PASS):

// In SelectableClicked, after setting SelectedItem:
for (int i = 0; i < _currentViewHolders.Count; i++)
{
    var holder = _currentViewHolders[i];
    if (holder.BindingAdapterPosition == adapterPosition)
        holder.IsSelected = true;
    else
        holder.IsSelected = false;
}

• Position-driven, not value-equality-driven
• Safe with scrolling/recycling (checks BindingAdapterPosition)
• Unconditional — handles both the equal-value case AND the normal case
• Also requires fixing the test with Equals/GetHashCode on Issue20062_Item

Recommended Changes for PR Author

1. Fix the test — Add Equals/GetHashCode to Issue20062_Item based on Name so the test actually reproduces the bug:

   public override bool Equals(object obj) =>
       obj is Issue20062_Item other && Name == other.Name;
   public override int GetHashCode() =>
       Name?.GetHashCode(StringComparison.Ordinal) ?? 0;

2. Fix the code — Replace the fragile index-based ViewHolder lookup with a position-matching loop:

   case SelectionMode.Single:
       ItemsView.SelectedItem = ItemsSource.GetItem(adapterPosition);
       for (int i = 0; i < _currentViewHolders.Count; i++)
       {
           var holder = _currentViewHolders[i];
           holder.IsSelected = (holder.BindingAdapterPosition == adapterPosition);
       }
       return;

3. Minor: Add newline at end of TestCases.Shared.Tests/Tests/Issues/Issue20062.cs

4. Consider: The [Issue] attribute says PlatformAffected.Android but the test also runs on iOS and Mac. The iOS test was noted as failing (different snapshot issue). Clarify platform scope or address iOS behavior separately.

Fix Candidates

#	Source	Approach	Test Result	Recommendation
PR	PR #31591	Equality check + direct list index	⚠️ BLOCKED	Don't use — fragile index
4	Attempt-4 (gemini)	Position-driven loop + test fix	✅ PASS	Recommended

Selected Fix: Attempt 4 (not PR's fix)

---

📋 Expand PR Finalization Review

PR #31591 Finalization Review

PR: CollectionView - SelectedItem visual state manager not working
Author: KarthikRajaKalaimani
Base: main
Labels: area-controls-collectionview, community ✨, partner/syncfusion, s/agent-reviewed, s/agent-changes-requested, s/agent-gate-failed, s/agent-fix-pr-picked

---

Phase 1: Title & Description

🟡 Title: Needs Update

Current: CollectionView - SelectedItem visual state manager not working
Issue: Reads like an issue title, not a commit/fix title. Doesn't describe the fix or scope.
Recommended: [Android] CollectionView: Fix SelectedItem visual state not applying when re-selecting same item

✅ Description: Good — Keep With Minor Additions

Quality assessment:

Dimension	Assessment
NOTE block	✅ Present at top
Root cause	✅ Clear explanation of the equality-check bypass
Description of change	✅ Step-by-step description of the fix approach
Platform testing	✅ Checkboxes shown (Android ✅, iOS ✅, Mac ✅, Windows ❌)
Videos	✅ Before/after recordings included
Issues Fixed	✅ Fixes #20062 present

Minor additions that would improve it:

1. Clarify the exact trigger condition — The description says "duplicate values (e.g., all string 'a' items)" but the root cause is also triggered when tapping the same already-selected item again. This more common case should be mentioned.

2. Add a "What NOT to Do" note about the index-based _currentViewHolders[viewHolderIndex] approach (see Code Review below), so future agents don't accidentally extend this pattern.

---

Phase 2: Code Review

🔴 Critical Issue — Unsafe ViewHolder Index Access

File: src/Controls/src/Core/Handlers/Items/Android/Adapters/SelectableItemsViewAdapter.cs
Lines: 185–187

var viewHolderIndex = ItemsSource.HasHeader ? adapterPosition - 1 : adapterPosition;
ClearPlatformSelection();
_currentViewHolders[viewHolderIndex].IsSelected = true;

Problem: _currentViewHolders is a List<SelectableViewHolder> that tracks currently bound ViewHolders. ViewHolders are appended when bound (OnBindViewHolder) and removed when recycled (OnViewRecycled). The order in this list is the order of binding, NOT the adapter position order. After any scrolling or recycling, the index of a holder in the list will not match its adapter position.

This means _currentViewHolders[viewHolderIndex] will set IsSelected = true on the wrong ViewHolder any time scrolling has occurred or items have been recycled and rebound in a different order.

Comparison: The existing MarkPlatformSelection method (lines 102–113) correctly avoids this assumption by iterating all holders and using holder.BindingAdapterPosition to look up the item at each position:

for (int i = 0; i < _currentViewHolders.Count; i++)
{
    var holder = _currentViewHolders[i];
    if (holder.BindingAdapterPosition >= 0)
    {
        var item = ItemsSource.GetItem(holder.BindingAdapterPosition);
        bool shouldBeSelected = _selectedSet.Contains(item);
        if (holder.IsSelected != shouldBeSelected)
            holder.IsSelected = shouldBeSelected;
    }
}

Recommended Fix: Replace the positional index lookup with a BindingAdapterPosition search, matching the established pattern:

case SelectionMode.Single:
    var previouslySelectedItem = ItemsView.SelectedItem;
    ItemsView.SelectedItem = ItemsSource.GetItem(adapterPosition);
    if (previouslySelectedItem == ItemsView.SelectedItem && ItemsView.SelectedItem is not null)
    {
        ClearPlatformSelection();
        for (int i = 0; i < _currentViewHolders.Count; i++)
        {
            if (_currentViewHolders[i].BindingAdapterPosition == adapterPosition)
            {
                _currentViewHolders[i].IsSelected = true;
                break;
            }
        }
    }
    return;

Why the test still passes with the broken code: The test only has 4 items, all visible at once, and no scrolling. ViewHolders are bound in position order (0, 1, 2, 3) with no recycling, so the positional index accidentally matches. Real-world CollectionViews with more items and scrolling will exhibit incorrect visual states.

---

🟡 Minor Issue — Missing Newline at End of File

File: src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue20062.cs

The file ends with #endif but no trailing newline. Many editors and linters warn about this; a newline should be added.

---

🟡 Minor Issue — PlatformAffected.Android Mismatch

File: src/Controls/tests/TestCases.HostApp/Issues/Issue20062.cs

[Issue(IssueTracker.Github, 20062, "...", PlatformAffected.Android)]

The PR adds snapshots for iOS and Mac (ios/CollectionViewSelectionChangesVisualState.png, mac/CollectionViewSelectionChangesVisualState.png) and the test is confirmed working on those platforms. The PlatformAffected attribute should reflect this:

[Issue(IssueTracker.Github, 20062, "...", PlatformAffected.Android | PlatformAffected.iOS | PlatformAffected.macOS)]

---

✅ Looks Good

• The root cause identification is correct: Android's SelectedItem setter uses value equality, so setting the same item (or equal item) does not trigger PropertyChanged, which means VisualStateManager.GoToState("Selected") is never called on the new selection's ViewHolder.
• ClearPlatformSelection() is an existing internal method — appropriate to reuse it here.
• The previouslySelectedItem is not null guard is correct to avoid interfering with the clear-selection case.
• Test page is well-structured using TestContentPage with the Init() override pattern.
• Test uses #if TEST_FAILS_ON_WINDOWS correctly per project conventions.
• VisualStateManager groups are defined in C# inline (no XAML required) — appropriate for a C#-only test page.

---

Summary

Area	Status	Action Required
Title	🟡 Update	Change to [Android] CollectionView: Fix SelectedItem visual state not applying when re-selecting same item
Description	✅ Keep	Add clarification on re-tap trigger; rest is excellent
Code — ViewHolder index	🔴 Critical	Replace positional index with BindingAdapterPosition search (pattern already exists in MarkPlatformSelection)
Code — Missing newline	🟡 Minor	Add newline at end of test file
Code — PlatformAffected	🟡 Minor	Expand to include iOS and macOS

Verdict: PR has a critical correctness bug in the fix logic (_currentViewHolders[viewHolderIndex] is index-unsafe). The fix works in the test because the test uses a small non-scrolling list, but will silently select the wrong item's visual state in production CollectionViews with scrolling. Changes are requested before merge.

[kubaflo]

Hi! Could you please review the AI's suggestions?

[MauiBot]

🚦 Gate - Test Before and After Fix

📊 Expand Full Gate — 00872d1 · Fix improved and test case modified

---

Gate Result: ✅ PASSED

Platform: ANDROID · Base: main · Merge base: 720a9d4a

Test	Without Fix (expect FAIL)	With Fix (expect PASS)
🖥️ Issue20062 Issue20062	✅ FAIL — 1636s	✅ PASS — 514s

🔴 Without fix — 🖥️ Issue20062: FAIL ✅ · 1636s

(truncated to last 15,000 chars)

tFramework=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:15:31.22
* 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.13698660
  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.13698660
  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.13698660
  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.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Maps -> /home/vsts/work/1/s/artifacts/bin/Maps/Debug/net10.0-android36.0/Microsoft.Maui.Maps.dll
  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.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  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
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Foldable.dll
  Controls.Xaml -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Xaml.dll

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

Time Elapsed 00:08:30.95
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/Controls/tests/CustomAttributes/Controls.CustomAttributes.csproj (in 1.41 sec).
  Restored /home/vsts/work/1/s/src/TestUtils/src/VisualTestUtils/VisualTestUtils.csproj (in 3 ms).
  Restored /home/vsts/work/1/s/src/TestUtils/src/VisualTestUtils.MagickNet/VisualTestUtils.MagickNet.csproj (in 4.06 sec).
  Restored /home/vsts/work/1/s/src/Controls/tests/TestCases.Android.Tests/Controls.TestCases.Android.Tests.csproj (in 5.7 sec).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.Core/UITest.Core.csproj (in 2 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 343 ms).
  Restored /home/vsts/work/1/s/src/TestUtils/src/UITest.Analyzers/UITest.Analyzers.csproj (in 2.33 sec).
  5 of 13 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  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.13698660
  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.13698660
  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.10]   Discovering: Controls.TestCases.Android.Tests
[xUnit.net 00:00:00.29]   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
>>>>> 03/31/2026 11:29:31 FixtureSetup for Issue20062(Android)
>>>>> 03/31/2026 11:29:33 CollectionViewSelectionChangesVisualState Start
>>>>> 03/31/2026 11:29:40 CollectionViewSelectionChangesVisualState Stop
>>>>> 03/31/2026 11:29:40 Log types: logcat, bugreport, server
  Failed CollectionViewSelectionChangesVisualState [8 s]
  Error Message:
   VisualTestUtils.VisualTestFailedException : 
Snapshot different than baseline: CollectionViewSelectionChangesVisualState.png (24.17% 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.Issue20062.CollectionViewSelectionChangesVisualState() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue20062.cs:line 22
   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

Test Run Failed.
Total tests: 1
     Failed: 1
 Total time: 31.0140 Seconds

🟢 With fix — 🖥️ Issue20062: PASS ✅ · 514s

  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.Foldable/Debug/net10.0-android36.0/Microsoft.Maui.Controls.Foldable.dll
  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.13698660
  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.13698660
  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.13698660
  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.13698660
  Core -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Controls.BindingSourceGen -> /home/vsts/work/1/s/artifacts/bin/Controls.BindingSourceGen/Debug/netstandard2.0/Microsoft.Maui.Controls.BindingSourceGen.dll
  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.13698660
  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.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Controls.Foldable -> /home/vsts/work/1/s/artifacts/bin/Controls.TestCases.HostApp/Debug/net10.0-android/Microsoft.Maui.Controls.Foldable.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.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.13698660
  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:06:38.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...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Controls.CustomAttributes -> /home/vsts/work/1/s/artifacts/bin/Controls.CustomAttributes/Debug/net10.0/Controls.CustomAttributes.dll
  Graphics -> /home/vsts/work/1/s/artifacts/bin/Graphics/Debug/net10.0/Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  Essentials -> /home/vsts/work/1/s/artifacts/bin/Essentials/Debug/net10.0/Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13698660
  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.13698660
  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
  VisualTestUtils.MagickNet -> /home/vsts/work/1/s/artifacts/bin/VisualTestUtils.MagickNet/Debug/netstandard2.0/VisualTestUtils.MagickNet.dll
  UITest.NUnit -> /home/vsts/work/1/s/artifacts/bin/UITest.NUnit/Debug/net10.0/UITest.NUnit.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.10]   Discovering: Controls.TestCases.Android.Tests
[xUnit.net 00:00:00.44]   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
>>>>> 03/31/2026 11:38:14 FixtureSetup for Issue20062(Android)
>>>>> 03/31/2026 11:38:16 CollectionViewSelectionChangesVisualState Start
>>>>> 03/31/2026 11:38:21 CollectionViewSelectionChangesVisualState Stop
  Passed CollectionViewSelectionChangesVisualState [5 s]
NUnit Adapter 4.5.0.0: Test execution complete

Test Run Successful.
Total tests: 1
     Passed: 1
 Total time: 21.3249 Seconds

📁 Fix files reverted (2 files)

• eng/pipelines/ci-copilot.yml
• src/Controls/src/Core/Handlers/Items/Android/Adapters/SelectableItemsViewAdapter.cs

---

[MauiBot]

🤖 AI Summary

📊 Expand Full Review — 00872d1 · Fix improved and test case modified

---

🔍 Pre-Flight — Context & Validation

---

Issue: #20062 - CollectionView - SelectedItem visual state manager not working
PR: #31591 - [Android] CollectionView: Fix SelectedItem visual state not applying when re-selecting same item
Platforms Affected: Android (primary fix), issue also mentions iOS
Files Changed: 1 implementation (Android), 1 HostApp test, 1 shared test, 3 snapshot images

Key Findings

• Root cause: BindableProperty.SetValue skips PropertyChanged notification when the new value equals the current value. When all CollectionView items are value-equal strings ("a"), tapping any item after the first leaves SelectedItem unchanged ("a" == "a"), so no PropertyChanged fires and VisualStateManager.GoToState("Selected") is never called on the newly-tapped ViewHolder.
• PR's fix: In SelectableClicked, after calling UpdateMauiSelection, unconditionally call ClearPlatformSelection() + clickedHolder.IsSelected = true for SelectionMode.Single. The clickedHolder is obtained directly from sender (the ViewHolder raises Clicked?.Invoke(this, adapterPosition) in OnViewHolderClicked), so this is a correct, non-fragile reference.
• Improvement over prior review: Previous agent noted the fix used _currentViewHolders[adapterPosition] (fragile index). Current version uses sender is SelectableViewHolder clickedHolder — the actual clicked holder — which is correct and safe during recycling.
• Unconditional application: The fix runs for ALL Single mode clicks, not just value-equal ones. For non-duplicate items: redundant (MarkPlatformSelection already ran) but harmless. For duplicate items: essential.
• Test uses string-based items: List<string> with all "a" values, creating the exact value-equal scenario. Test taps item 0 then item 2, verifies via screenshot that item 2 is visually selected and item 0 is deselected.
• iOS test concern: Reviewer jsuarezruiz noted iOS test failures; author updated iOS snapshot. The [Issue] attribute says PlatformAffected.Android but the test has no TEST_FAILS_ON_IOS/TEST_FAILS_ON_MAC guards.
• Gate: Current run PASSED (tests fail without fix, pass with fix) — previous agent run failed.
• Code formatting: Fix uses mixed tabs/spaces indentation unlike surrounding code.
• Prior agent labels: s/agent-reviewed, s/agent-changes-requested, s/agent-gate-failed, s/agent-fix-pr-picked — all indicating prior review and iteration.
• No newline at end of TestCases.Shared.Tests/Tests/Issues/Issue20062.cs.

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #31591	After UpdateMauiSelection, unconditionally call ClearPlatformSelection() + sender ViewHolder's IsSelected = true for Single mode	✅ PASSED (Gate)	SelectableItemsViewAdapter.cs	Uses sender directly — correct and recycling-safe

---

🔧 Fix — Analysis & Comparison

---

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
1	try-fix (opus)	In UpdateMauiSelection: capture previousItem, detect value-equality, then ClearPlatformSelection() + position-iterate _currentViewHolders by BindingAdapterPosition	✅ PASS	SelectableItemsViewAdapter.cs	Conditional; correct recycling-safe position lookup
2	try-fix (sonnet)	Add _selectedAdapterPosition field; fix MarkPlatformSelection Single branch to position-based match; force MarkPlatformSelection call in SelectableClicked	✅ PASS	SelectableItemsViewAdapter.cs	Most comprehensive — also fixes latent multi-select bug for value-equal items
3	try-fix (codex)	Force SelectedItem null→value transition to trigger PropertyChanged	❌ FAIL (24.17% visual diff)	SelectableItemsViewAdapter.cs	Null transition causes animation/state artifact in snapshot
4	try-fix (gpt-5.4, sub for gemini)	Conditional in SelectableClicked: if Equals(SelectedItem, newItem) before UpdateMauiSelection, force visual via sender ViewHolder	✅ PASS	SelectableItemsViewAdapter.cs	Conditional version of PR's fix; stricter trigger
PR	PR #31591	In SelectableClicked: after UpdateMauiSelection, unconditionally ClearPlatformSelection() + sender as SelectableViewHolder.IsSelected = true	✅ PASSED (Gate)	SelectableItemsViewAdapter.cs	Simplest; uses sender directly; unconditional but harmless

Cross-Pollination

Model	Round	New Ideas?	Details
claude-opus-4.6	2	NO NEW IDEAS	Attempt 1 clean; PR unconditional also works
claude-sonnet-4.6	2	NO NEW IDEAS	Attempt 2 most complete; PR acceptable minimal fix
gpt-5.3-codex	2	NO NEW IDEAS	Null-transition confirmed wrong approach
gpt-5.4	2	NO NEW IDEAS	Conditional stricter than PR; both pass

Exhausted: Yes
Selected Fix: PR's fix — Simplest minimal change, Gate passed, uses sender directly (recycling-safe). Attempt 2 reveals a latent MarkPlatformSelection bug worth noting as a future improvement.

---

📋 Report — Final Recommendation

---

✅ Final Recommendation: APPROVE

Phase Status

Phase	Status	Notes
Pre-Flight	✅ COMPLETE	Issue #20062, Android CollectionView value-equal selection bug
Gate	✅ PASSED	android — tests fail without fix, pass with fix
Try-Fix	✅ COMPLETE	4 attempts: 3 passing, 1 failing; gemini unavailable (gpt-5.4 substituted)
Report	✅ COMPLETE

Summary

PR #31591 fixes a long-standing Android CollectionView bug (issue #20062) where tapping a different item that has the same value as the currently selected item fails to update the visual selection state. The fix is minimal, targeted, and correctly uses the sender ViewHolder directly — avoiding the fragile index-based lookup from the prior version of this PR. Gate passed: the added UI test fails without the fix and passes with it.

Root Cause

BindableProperty.SetValue suppresses PropertyChanged when the new value is reference- or value-equal to the current. In UpdateMauiSelection, ItemsView.SelectedItem = item with two identical string "a" values results in no change notification, so MarkPlatformSelection is never called, and VisualStateManager.GoToState("Selected") never fires on the newly-tapped SelectableViewHolder.

Fix Quality

Good. The PR adds 10 lines in SelectableClicked: after UpdateMauiSelection, it unconditionally calls ClearPlatformSelection() + sets clickedHolder.IsSelected = true for SelectionMode.Single. The clickedHolder is obtained from the sender parameter, which is the actual SelectableViewHolder that raised the Clicked event (Clicked?.Invoke(this, adapterPosition) in OnViewHolderClicked). This is recycling-safe.

Try-Fix found two additional passing approaches: a conditional fix in UpdateMauiSelection (Attempt 1) and a more comprehensive fix that also corrects a latent bug in MarkPlatformSelection where value-equal items could all be marked as selected (Attempt 2). The PR's unconditional approach is safe: for normal (non-duplicate) items, MarkPlatformSelection has already run synchronously before the fix code executes, making the redundant call harmless. Selected Fix: PR's fix.

Issues to address before merge:

1. Mixed tabs/spaces indentation — the fix block at lines 174–183 uses spaces where the surrounding code uses tabs. This should be reformatted to tabs.

2. No newline at end of TestCases.Shared.Tests/Tests/Issues/Issue20062.cs — file ends without a trailing newline.

3. [Issue] attribute says PlatformAffected.Android but test runs on iOS and Mac — the test has no TEST_FAILS_ON_IOS or TEST_FAILS_ON_MAC guards. The iOS snapshot was updated after a reviewer-reported failure. Since the underlying code fix is Android-only, either add iOS/Mac guards or confirm iOS/Mac behavior is intentionally tested.

4. FindElementsByText("a") fragility — the test locates all 4 items by their displayed text "a" and taps by index. With a 2-column GridItemsLayout, this is currently deterministic with 4 items, but could be brittle if the test page is ever changed. Consider using AutomationId on individual cells for more reliable tapping.

5. Latent MarkPlatformSelection bug (future work) — when SelectedItem = "a" and all items are "a", MarkPlatformSelection would mark all holders as selected because _selectedSet.Contains("a") is true for every holder. This isn't triggered by the current test flow (no PropertyChanged fires for equal items), but it could surface in other scenarios. Consider a follow-up fix (Attempt 2's approach) to make MarkPlatformSelection position-aware for Single mode.

---

[kubaflo]

Could you review the ai's summary please?

[KarthikRajaKalaimani]

Could you review the ai's summary please?

Addressed the AI summary concerns.

[sheiksyedm]

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

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).