[Windows] Fix Indicator View Causing Looping Issue with CarouselView

[Tamilarasan-Paranthaman]

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 of the issue

• In the UpdateCurrentItem method, the view scrolls to the current item position. When the item position is updated from the IndicatorView, it triggers the Scrolled event, which then updates the position based on the current index. In the UpdatePosition method, the current item is continuously updated even while the view is still in a scrolling state, leading to an infinite scrolling loop and other position related issues.

Description of Change

• Introduced a _lastScrolledToPosition tracking field to prevent re-entrant ScrollTo calls that cause the infinite loop.
• Modified UpdateCurrentItem to only issue ScrollTo when the position actually differs AND has not already been scrolled to.
• Added ScrollTo in UpdatePosition (guarded by IsDragging/IsScrolling checks) so IndicatorView-driven position changes scroll the carousel correctly.
• Reset the tracker on user scrolling (CarouselScrolled) and collection source changes (OnCollectionItemsSourceChanged).
• Removed the Loop centering code from UpdateInitialPosition (see code review note about potential regression).

Why tests are restricted on Windows and Mac:

• The test added in this PR for Issue27563 is currently restricted on Windows and MacCatalyst because it relies on Appium-driven CarouselView swipe/position behavior, which is not reliable on these platforms.
• For Windows, this aligns with the existing issue tracked in [Testing] Appium test does not perform the tap action with CarouselView. #29245, where CarouselView automation leads to timeouts and failures unrelated to the fix. Once this issue is resolved, we can remove the platform restriction.
• Keeping the test behind platform guards helps avoid introducing known UI test flakiness into the PR.

Issues Fixed

Fixes #27563
Fixes #22468
Fixes #7149

Tested the behaviour in the following platforms

• Windows
• Android
• iOS
• Mac

Screenshot

Before Issue Fix	After Issue Fix
Before-Fix.mp4	After-Fix.mp4

[jsuarezruiz]

/rebase

[jsuarezruiz]

/rebase

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

The test is failing on Mac and Windows:

   at UITest.Appium.HelperExtensions.Wait(Func`1 query, Func`2 satisfactory, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2367
   at UITest.Appium.HelperExtensions.WaitForAtLeastOne(Func`1 query, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 2384
   at UITest.Appium.HelperExtensions.WaitForElement(IApp app, String marked, String timeoutMessage, Nullable`1 timeout, Nullable`1 retryFrequency, Nullable`1 postTimeout) in /_/src/TestUtils/src/UITest.Appium/HelperExtensions.cs:line 665
   at Microsoft.Maui.TestCases.Tests.Issues.Issue27563.VerifyCarouselViewScrolling() in /_/src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue27563.cs:line 21
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

[Tamilarasan-Paranthaman]

The test failed with a timeout exception on both Windows and Mac.

On Mac, this appears to be due to the lack of support for SwipeRightToLeft. We can modify the test case specifically for the Mac platform.

On Windows, the test ran for an extended period before failing with a timeout exception.

I conducted further testing on a local machine and found that the test passed when CarouselView.Loop was set to false. This suggests that the issue occurs only when CarouselView.Loop is set to true. Additionally, I identified other test cases where Loop is enabled, and they also include the TEST_FAILS_ON_WINDOWS condition referencing this issue (e.g., Script: 12574 - Sample - 12574).

However, in the CI environment, the failure when Loop is enabled appears to be due to a different issue.

@jsuarezruiz, could you please share your insights on this and suggest how we should proceed on Windows platforms?

[dhindrik]

@jsuarezruiz @Tamilarasan-Paranthaman is there a way forward with this PR?

[bronteq]

@jsuarezruiz friendly ping

[jsuarezruiz]

/rebase

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[jsuarezruiz]

Rebased and running a new build.

[jsuarezruiz]

Can extend the new test to cover loop initial centering and the reentrancy case (tap indicator repeatedly while swiping), and a test that toggles Position to the same value to ensure no scroll storm occurs.

[kubaflo]

Hi, is this still valid?

[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 -- 27880

Or

• Run remotely in PowerShell:

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

[Vignesh-SF3580]

Hi, is this still valid?

@kubaflo I have verified this on my end, and it is still valid PR. The issue still reproduces on the latest main source and is resolved by the changes made in this PR.

Without Fix	With Fix
WithoutFix27880.mp4	WithFix27880.mp4

[kubaflo]

📋 PR Finalization Review

Title: ✅ Good

Current: [Windows] Fix Indicator View Causing Looping Issue with CarouselView

Description: ⚠️ Needs Update

The description has good technical content:

• ✅ Clear root cause explanation (ScrollTo → Scrolled → UpdatePosition loop)

• ✅ Description of change with rationale

• ✅ Issues Fixed section (3 issues)

• ✅ Platform testing matrix (all 4 platforms)

• ✅ Before/after video comparisons

• ❌ Missing required NOTE block at the top for testing PR artifacts

• 🟡 Claim about 'aligning with Android' is imprecise — Android CarouselViewHandler delegates to MauiCarouselRecyclerView with a fundamentally different architecture; the behavioral outcome is similar but the implementation pattern is different
  Missing Elements:

• Required NOTE block must be prepended at the top of the description (this is mandatory for all PRs)

• Otherwise the existing description is solid and should be preserved

✨ Suggested PR Description

[!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 of the issue

• In the UpdateCurrentItem method, the view scrolls to the current item position. When the item position is updated from the IndicatorView, it triggers the Scrolled event, which then updates the position based on the current index. In the UpdatePosition method, the current item is continuously updated even while the view is still in a scrolling state, leading to an infinite scrolling loop and other position related issues.

Description of Change

• Introduced a _lastScrolledToPosition tracking field to prevent re-entrant ScrollTo calls that cause the infinite loop.
• Modified UpdateCurrentItem to only issue ScrollTo when the position actually differs AND has not already been scrolled to.
• Added ScrollTo in UpdatePosition (guarded by IsDragging/IsScrolling checks) so IndicatorView-driven position changes scroll the carousel correctly.
• Reset the tracker on user scrolling (CarouselScrolled) and collection source changes (OnCollectionItemsSourceChanged).
• Removed the Loop centering code from UpdateInitialPosition (see code review note about potential regression).

Issues Fixed

Fixes #27563
Fixes #22468
Fixes #7149

Tested the behaviour in the following platforms

• Windows
• Android
• iOS
• Mac

Screenshot

Before Issue Fix	After Issue Fix
Before-Fix.mp4	After-Fix.mp4

Code Review: ⚠️ Issues Found

🔴 Critical Issues

1. Removed Loop centering code in UpdateInitialPosition

• File: src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs
• Problem: The original code had a block that set _loopableCollectionView.CenterMode = true, called ListViewBase.ScrollIntoView(item), then reset CenterMode = false when Element.Loop was enabled. This entire block was removed. For Loop mode, the carousel needs to be centered in the virtualized list to allow bi-directional scrolling. Without this, Loop mode initial positioning may regress on Windows.
• Recommendation: Verify that Loop mode still works correctly on initial load. If the centering was removed intentionally, add a code comment explaining why it is no longer needed.

2. UI test excluded from Windows — the target platform

• File: src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/Issue27563.cs
• Problem: The test uses #if TEST_FAILS_ON_WINDOWS && TEST_FAILS_ON_CATALYST which excludes it from both Windows and MacCatalyst. Since this is a Windows-targeted fix, the test cannot verify the fix on the platform it targets. The comment references issue [Testing] Appium test does not perform the tap action with CarouselView. #29245 (TimeoutException with Loop), but the test page does not even use Loop = true.
• Recommendation: Investigate whether the Windows exclusion is still necessary. If the Loop-related issue ([Testing] Appium test does not perform the tap action with CarouselView. #29245) does not affect this test scenario (no Loop in the test page), consider removing the Windows exclusion so CI validates the fix on Windows.

🟡 Suggestions

1. Snapshot label shows stale position — Both Android and iOS reference snapshots show "CarouselView Position - 0" even though the carousel is visually at position 2 ("Percentage View"). The HostApp button handler reads carousel.Position synchronously after setting indicatorView.Position = 2, before the carousel finishes scrolling. Consider using a PropertyChanged handler on CarouselView.Position to update the label asynchronously for accurate snapshot verification.

2. CarouselScrolled reset edge case — The tracker reset (_lastScrolledToPosition = -1) in CarouselScrolled only fires when position != _lastScrolledToPosition. If a user manually scrolls back to the same position the tracker already holds, it will not reset, which could prevent a subsequent programmatic scroll to that index.

3. Missing newline at end of file — Both Issue27563.cs files (HostApp and Shared.Tests) are missing a trailing newline.

✅ Looks Good

1. The _lastScrolledToPosition tracking mechanism is a clean, effective approach to break the infinite ScrollTo → Scrolled → UpdatePosition loop
2. Good use of IsDragging and IsScrolling guards in UpdatePosition to prevent programmatic scrolls during user interaction
3. Proper reset of _lastScrolledToPosition in OnCollectionItemsSourceChanged ensures stale state does not persist after data changes
4. The HostApp test page uses C# only (preferred pattern), has correct AutomationId attributes, and appropriate [Issue] attribute
5. Single [Category(UITestCategories.CarouselView)] on the test (correct per guidelines)
6. Fixes 3 long-standing related issues ([Windows] Indicator view causes looping with CarouselView #27563, CarouselView behaves strangely when manipulating position in ViewModel #22468, [Windows] [Scenario Day] Scroll by Object not working the first time #7149) with a single cohesive approach

[Vignesh-SF3580]

📋 PR Finalization Review

Title: ✅ Good

Current: [Windows] Fix Indicator View Causing Looping Issue with CarouselView

Description: ⚠️ Needs Update

The description has good technical content:

• ✅ Clear root cause explanation (ScrollTo → Scrolled → UpdatePosition loop)
• ✅ Description of change with rationale
• ✅ Issues Fixed section (3 issues)
• ✅ Platform testing matrix (all 4 platforms)
• ✅ Before/after video comparisons
• ❌ Missing required NOTE block at the top for testing PR artifacts
• 🟡 Claim about 'aligning with Android' is imprecise — Android CarouselViewHandler delegates to MauiCarouselRecyclerView with a fundamentally different architecture; the behavioral outcome is similar but the implementation pattern is different
  Missing Elements:
• Required NOTE block must be prepended at the top of the description (this is mandatory for all PRs)
• Otherwise the existing description is solid and should be preserved

✨ Suggested PR Description

[!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 of the issue

• In the UpdateCurrentItem method, the view scrolls to the current item position. When the item position is updated from the IndicatorView, it triggers the Scrolled event, which then updates the position based on the current index. In the UpdatePosition method, the current item is continuously updated even while the view is still in a scrolling state, leading to an infinite scrolling loop and other position related issues.

Description of Change

• Introduced a _lastScrolledToPosition tracking field to prevent re-entrant ScrollTo calls that cause the infinite loop.
• Modified UpdateCurrentItem to only issue ScrollTo when the position actually differs AND has not already been scrolled to.
• Added ScrollTo in UpdatePosition (guarded by IsDragging/IsScrolling checks) so IndicatorView-driven position changes scroll the carousel correctly.
• Reset the tracker on user scrolling (CarouselScrolled) and collection source changes (OnCollectionItemsSourceChanged).
• Removed the Loop centering code from UpdateInitialPosition (see code review note about potential regression).

Issues Fixed

Fixes #27563 Fixes #22468 Fixes #7149

Tested the behaviour in the following platforms

• Windows
• Android
• iOS
• Mac

Screenshot

Before Issue Fix After Issue Fix
Before-Fix.mp4
After-Fix.mp4
Code Review: ⚠️ Issues Found

• The CenterMode/ScrollIntoView loop centering block was intentionally removed. Centering is now handled programmatically by UpdateCurrentItem and UpdatePosition using the _lastScrolledToPosition guard, making the previous block redundant. A code comment was added to explain this.

• The UI test is excluded from Windows due to a known issue where CarouselView.Loop causes a TimeoutException on Windows CI (tracked in [Testing] Appium test does not perform the tap action with CarouselView. #29245). The test comment already references [Testing] Appium test does not perform the tap action with CarouselView. #29245, so no further improvement is needed.

[MauiBot]

🤖 AI Summary

📊 Expand Full Review — f26b850 · tests updated.

---

🔍 Pre-Flight — Context & Validation

---

Issue: #27563 - [Windows] Indicator view causes looping with CarouselView
PR: #27880 - [Windows] Fix Indicator View Causing Looping Issue with CarouselView
Platforms Affected: Windows (fix in CarouselViewHandler.Windows.cs)
Files Changed: 1 implementation, 2 test files, 2 snapshot PNGs

Key Findings

• Root Cause: UpdateCurrentItem unconditionally called ScrollTo, which fired CarouselScrolled, which updated Position, which triggered UpdatePosition, which called ScrollTo again — creating an infinite loop when IndicatorView changes position.
• Fix Approach: Introduced _lastScrolledToPosition field (int, init -1) to guard against re-entrant ScrollTo calls in both UpdateCurrentItem and UpdatePosition.
• Removed Loop centering: The UpdateInitialPosition method no longer explicitly handles Loop = true CenterMode scrolling; the PR asserts this is made redundant by the new guard. This is a potential regression for Loop mode.
• Test exclusion: Both new tests are excluded on Windows via #if !WINDOWS — the Windows-specific bug has no Windows test coverage. Gate FAILED because no Windows tests exist for this fix.
• Unresolved review thread: jsuarezruiz asked for tests covering loop initial centering, reentrancy with indicator tapping, and scroll-storm prevention for duplicate Position values. Thread is not resolved.
• Gate context: Gate ran on Windows; gate FAILED because the test is excluded on Windows. The bug being fixed is Windows-only.
• CarouselScrolled reset logic: When user scrolls and position != _lastScrolledToPosition, the tracker is reset to -1 (not to position). This means after user swipe, _lastScrolledToPosition == -1, so any subsequent programmatic scroll to any position will fire.

Concerns

1. Missing Windows test: A Windows-only fix with no Windows test. The gate cannot validate this fix.
2. Loop regression risk: Removed UpdateInitialPosition loop centering block without a dedicated test covering Loop+centering behavior.
3. CarouselScrolled reset logic gap: Resetting to -1 on position mismatch in CarouselScrolled means if user scrolls to position 2, then indicator programmatically sets position to 2 again, the guard allows it (since _lastScrolledToPosition == -1). This is correct behavior but may cause subtle issues.
4. UpdatePosition calls SetCarouselViewCurrentItem unconditionally after the ScrollTo guard, which is correct but may update CurrentItem even when not scrolling.

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
PR	PR #27880	_lastScrolledToPosition tracker field to gate re-entrant ScrollTo calls	❌ Gate FAILED (no Windows test)	CarouselViewHandler.Windows.cs	Tests excluded on Windows

---

🔧 Fix — Analysis & Comparison

---

Fix Candidates

#	Source	Approach	Test Result	Files Changed	Notes
1	try-fix (claude-opus-4.6)	_isProgrammaticScroll boolean flag + remove #if !WINDOWS	FAIL	2 files	WinAppDriver can't access elements inside CarouselView DataTemplate; 240s timeout
2	try-fix (claude-sonnet-4.6)	Test rewrite with external labels + layout reorder	FAIL	3 files	LoopableCollectionView floods UIA StructureChanged events; WinAppDriver hangs indefinitely
3	try-fix (gpt-5.3-codex)	CarouselScrollSyncState state machine + unit tests	PASS	3 files	10 unit tests; validates scroll guard logic without WinAppDriver dependency
4	try-fix (gpt-5.4)	Unsubscribe CarouselScrolled during programmatic ScrollTo + unit tests	PASS	2 files	8 unit tests; clean event suppression but brief window of missed events
5	try-fix (claude-sonnet-4.6)	_settingPositionFromScroll bool in SetCarouselViewPosition + unit tests	PASS	2 files	9 unit tests; targets exact re-entry point; minimal change
PR	PR #27880	_lastScrolledToPosition int tracker	Gate FAILED	1 file	Both tests excluded on Windows with #if !WINDOWS; no Windows test validates the fix

Cross-Pollination

Model	Round	New Ideas?	Details
claude-opus-4.6	2	Yes	Windows device test (Controls.DeviceTests bypasses WinAppDriver)
claude-sonnet-4.6	2	Yes	Equality guard at binding source (IndicatorView setter early exit)
gpt-5.3-codex	2	Yes	Versioned coalescing sync with origin/version tracking
claude-opus-4.6	3	Yes	IsIntermediate filtering on ViewChanged events
gpt-5.3-codex	3	Yes	Snap-point completion sync
gpt-5.4	3	Yes	SetValueFromRenderer instead of direct property assignment

Exhausted: Yes (3 rounds, 3 passing alternatives found)
Selected Fix: Candidate #5 (_settingPositionFromScroll bool) is the most targeted and minimal. However, the PR fix logic may also be correct primary issue is missing Windows test coverage and Loop regression risk. Recommendation: REQUEST CHANGES.

---

📋 Report — Final Recommendation

---

⚠️ Final Recommendation: REQUEST CHANGES

Phase Status

Phase	Status	Notes
Pre-Flight	✅ COMPLETE	Windows-only CarouselView+IndicatorView loop; 5 changed files
Gate	❌ FAILED	Windows — both tests excluded with #if !WINDOWS; no tests ran
Try-Fix	✅ COMPLETE	5 attempts; 3 passing alternatives found
Report	✅ COMPLETE

Summary

PR #27880 fixes a real Windows-specific bug (#27563) where CarouselView + IndicatorView creates an infinite scroll loop. The handler fix logic using _lastScrolledToPosition is conceptually sound, but the PR cannot be approved because:

1. Gate failed on Windows — both new tests are excluded with #if !WINDOWS, leaving the Windows-only bug completely unvalidated by automated tests
2. The UpdateInitialPosition Loop centering removal is an unreviewed regression risk
3. Three alternative fix approaches (attempts 3, 4, 5) all passed unit tests and provide better testability

Root Cause

The infinite loop: IndicatorView.Position = N → MapPosition → UpdatePosition → ItemsView.ScrollTo(N) → CarouselScrolled(N) → SetCarouselViewPosition(N) → ItemsView.Position = N → MapPosition → UpdatePosition → loop.

Fix Quality

PR's fix (_lastScrolledToPosition int tracker):

• ✅ Correct concept: prevents re-entrant ScrollTo calls
• ✅ Also handles OnCollectionItemsSourceChanged reset
• ❌ No Windows test coverage — both tests guarded by #if !WINDOWS
• ❌ Loop centering removed from UpdateInitialPosition without test coverage
• ❌ Reset logic in CarouselScrolled resets to -1 (not position) — subtle but correct

Best alternative (Attempt 5 — _settingPositionFromScroll bool):

• ✅ Most targeted: wraps ItemsView.Position = position in SetCarouselViewPosition with a flag
• ✅ Guards the exact re-entry point (synchronous MAUI property callbacks)
• ✅ Cannot be corrupted by intermediate position values (unlike int tracker)
• ✅ finally block guarantees cleanup
• ✅ 9 unit tests validate the behavior
• ✅ Minimal: 2 files, ~15 lines

Windows test infrastructure finding:
Attempts 1 & 2 confirmed that Windows UI tests for CarouselView are structurally blocked: LoopableCollectionView fires continuous UIA StructureChanged events ~326ms after page load, causing WinAppDriver to hang indefinitely. This means the #if !WINDOWS guard, while wrong in principle, reflects a real infrastructure limitation. The correct path is Windows device tests (Controls.DeviceTests) which bypass WinAppDriver entirely.

Required Changes

1. Add Windows unit tests or device tests — The fix needs test coverage on Windows. Unit tests (dotnet test Core.UnitTests) are immediately viable and can validate the scroll guard logic without WinAppDriver.
2. Review Loop regression — The removed CenterMode block in UpdateInitialPosition needs a test or justification that Loop+initial position still works correctly.
3. Consider simpler alternative — The _settingPositionFromScroll approach (attempt 5 diff in try-fix/attempt-5/fix.diff) is cleaner and more directly targets the re-entry path.
4. Address unresolved review thread — jsuarezruiz requested tests covering loop initial centering, reentrancy with indicator tapping, and scroll-storm prevention (thread unresolved).

Selected Fix: PR's fix (with required test additions) — the underlying approach is valid; tests are missing.

---

[Vignesh-SF3580]

🤖 AI Summary

📊 Expand Full Review — ce189d0 · Update CarouselViewHandler.Windows.cs

The concern in the AI summary is that the fix is specific to Windows, but the test is restricted on Windows. The AI suggested adding a Windows test to validate the fix.
However, we are facing issue (#29245) on Windows when enabling loop, so the test has been restricted on that platform. I have already documented the details in the test case comments and updated the PR description.
Since a reliable Windows test is not currently feasible, the test remains restricted on Windows.

[MauiBot]

🚦 Gate - Test Before and After Fix

📊 Expand Full Gate — f26b850 · tests updated.

---

Gate Result: ❌ FAILED

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

Test	Without Fix (expect FAIL)	With Fix (expect PASS)
🖥️ Issue27563 Issue27563	✅ FAIL — 518s	❌ FAIL — 425s

🔴 Without fix — 🖥️ Issue27563: FAIL ✅ · 518s

  Determining projects to restore...
  Restored D:\a\1\s\src\Controls\src\Core\Controls.Core.csproj (in 39.66 sec).
  Restored D:\a\1\s\src\Controls\Maps\src\Controls.Maps.csproj (in 39.71 sec).
  Restored D:\a\1\s\src\Controls\Foldable\src\Controls.Foldable.csproj (in 251 ms).
  Restored D:\a\1\s\src\BlazorWebView\src\Maui\Microsoft.AspNetCore.Components.WebView.Maui.csproj (in 3.8 sec).
  Restored D:\a\1\s\src\Graphics\src\Graphics.Win2D\Graphics.Win2D.csproj (in 25 ms).
  Restored D:\a\1\s\src\Essentials\src\Essentials.csproj (in 16 ms).
  Restored D:\a\1\s\src\Core\src\Core.csproj (in 67 ms).
  Restored D:\a\1\s\src\Core\maps\src\Maps.csproj (in 25 ms).
  Restored D:\a\1\s\src\Graphics\src\Graphics\Graphics.csproj (in 3.95 sec).
  Restored D:\a\1\s\src\Controls\src\Xaml\Controls.Xaml.csproj (in 27 ms).
  Restored D:\a\1\s\src\Controls\tests\TestCases.HostApp\Controls.TestCases.HostApp.csproj (in 650 ms).
  3 of 14 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics.Win2D -> D:\a\1\s\artifacts\bin\Graphics.Win2D\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Foldable -> D:\a\1\s\artifacts\bin\Controls.Foldable\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Foldable.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> D:\a\1\s\artifacts\bin\Microsoft.AspNetCore.Components.WebView.Maui\Debug\net10.0-windows10.0.19041.0\Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.dll
  Controls.TestCases.HostApp -> D:\a\1\s\artifacts\bin\Controls.TestCases.HostApp\Debug\net10.0-windows10.0.19041.0\win-x64\Controls.TestCases.HostApp.dll

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

Time Elapsed 00:05:44.99
  Determining projects to restore...
  Restored D:\a\1\s\src\Controls\tests\CustomAttributes\Controls.CustomAttributes.csproj (in 872 ms).
  Restored D:\a\1\s\src\TestUtils\src\VisualTestUtils\VisualTestUtils.csproj (in 4 ms).
  Restored D:\a\1\s\src\TestUtils\src\VisualTestUtils.MagickNet\VisualTestUtils.MagickNet.csproj (in 5.65 sec).
  Restored D:\a\1\s\src\Controls\tests\TestCases.WinUI.Tests\Controls.TestCases.WinUI.Tests.csproj (in 8.43 sec).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Core\UITest.Core.csproj (in 2 ms).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Appium\UITest.Appium.csproj (in 2 ms).
  Restored D:\a\1\s\src\TestUtils\src\UITest.NUnit\UITest.NUnit.csproj (in 3.02 sec).
  Restored D:\a\1\s\src\TestUtils\src\UITest.Analyzers\UITest.Analyzers.csproj (in 5.14 sec).
  7 of 15 projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  Controls.CustomAttributes -> D:\a\1\s\artifacts\bin\Controls.CustomAttributes\Debug\net10.0\Controls.CustomAttributes.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0\Microsoft.Maui.dll
  Controls.Core.Design -> D:\a\1\s\artifacts\bin\Controls.Core.Design\Debug\net472\Microsoft.Maui.Controls.DesignTools.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0\Microsoft.Maui.Controls.dll
  UITest.Core -> D:\a\1\s\artifacts\bin\UITest.Core\Debug\net10.0\UITest.Core.dll
  UITest.Appium -> D:\a\1\s\artifacts\bin\UITest.Appium\Debug\net10.0\UITest.Appium.dll
  UITest.NUnit -> D:\a\1\s\artifacts\bin\UITest.NUnit\Debug\net10.0\UITest.NUnit.dll
  VisualTestUtils -> D:\a\1\s\artifacts\bin\VisualTestUtils\Debug\netstandard2.0\VisualTestUtils.dll
  VisualTestUtils.MagickNet -> D:\a\1\s\artifacts\bin\VisualTestUtils.MagickNet\Debug\netstandard2.0\VisualTestUtils.MagickNet.dll
  UITest.Analyzers -> D:\a\1\s\artifacts\bin\UITest.Analyzers\Debug\netstandard2.0\UITest.Analyzers.dll
  Controls.TestCases.WinUI.Tests -> D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
Test run for D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.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.
D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
   NUnit3TestExecutor discovered 0 of 0 NUnit test cases using Current Discovery mode, Explicit run
NUnit Adapter 4.5.0.0: Test execution complete
[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.08]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.27]   Discovered:  Controls.TestCases.WinUI.Tests
No test matches the given testcase filter `Issue27563` in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll

🟢 With fix — 🖥️ Issue27563: FAIL ❌ · 425s

  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics.Win2D -> D:\a\1\s\artifacts\bin\Graphics.Win2D\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Graphics.Win2D.WinUI.Desktop.dll
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Maps -> D:\a\1\s\artifacts\bin\Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Maps.dll
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Maps -> D:\a\1\s\artifacts\bin\Controls.Maps\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Maps.dll
  Microsoft.AspNetCore.Components.WebView.Maui -> D:\a\1\s\artifacts\bin\Microsoft.AspNetCore.Components.WebView.Maui\Debug\net10.0-windows10.0.19041.0\Microsoft.AspNetCore.Components.WebView.Maui.dll
  Controls.Xaml -> D:\a\1\s\artifacts\bin\Controls.Xaml\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Xaml.dll
  Controls.Foldable -> D:\a\1\s\artifacts\bin\Controls.Foldable\Debug\net10.0-windows10.0.19041.0\Microsoft.Maui.Controls.Foldable.dll
  Controls.TestCases.HostApp -> D:\a\1\s\artifacts\bin\Controls.TestCases.HostApp\Debug\net10.0-windows10.0.19041.0\win-x64\Controls.TestCases.HostApp.dll

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

Time Elapsed 00:05:32.03
  Determining projects to restore...
  All projects are up-to-date for restore.
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Graphics -> D:\a\1\s\artifacts\bin\Graphics\Debug\net10.0\Microsoft.Maui.Graphics.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Essentials -> D:\a\1\s\artifacts\bin\Essentials\Debug\net10.0\Microsoft.Maui.Essentials.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Core -> D:\a\1\s\artifacts\bin\Core\Debug\net10.0\Microsoft.Maui.dll
  Controls.CustomAttributes -> D:\a\1\s\artifacts\bin\Controls.CustomAttributes\Debug\net10.0\Controls.CustomAttributes.dll
  Controls.Core.Design -> D:\a\1\s\artifacts\bin\Controls.Core.Design\Debug\net472\Microsoft.Maui.Controls.DesignTools.dll
  Controls.BindingSourceGen -> D:\a\1\s\artifacts\bin\Controls.BindingSourceGen\Debug\netstandard2.0\Microsoft.Maui.Controls.BindingSourceGen.dll
  ##vso[build.updatebuildnumber]10.0.60-ci+azdo.13684418
  Controls.Core -> D:\a\1\s\artifacts\bin\Controls.Core\Debug\net10.0\Microsoft.Maui.Controls.dll
  VisualTestUtils -> D:\a\1\s\artifacts\bin\VisualTestUtils\Debug\netstandard2.0\VisualTestUtils.dll
  UITest.Core -> D:\a\1\s\artifacts\bin\UITest.Core\Debug\net10.0\UITest.Core.dll
  UITest.Appium -> D:\a\1\s\artifacts\bin\UITest.Appium\Debug\net10.0\UITest.Appium.dll
  UITest.NUnit -> D:\a\1\s\artifacts\bin\UITest.NUnit\Debug\net10.0\UITest.NUnit.dll
  VisualTestUtils.MagickNet -> D:\a\1\s\artifacts\bin\VisualTestUtils.MagickNet\Debug\netstandard2.0\VisualTestUtils.MagickNet.dll
  UITest.Analyzers -> D:\a\1\s\artifacts\bin\UITest.Analyzers\Debug\netstandard2.0\UITest.Analyzers.dll
  Controls.TestCases.WinUI.Tests -> D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
Test run for D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.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.
D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
NUnit Adapter 4.5.0.0: Test execution started
Running selected tests in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll
   NUnit3TestExecutor discovered 0 of 0 NUnit test cases using Current Discovery mode, Explicit run
NUnit Adapter 4.5.0.0: Test execution complete
[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.09]   Discovering: Controls.TestCases.WinUI.Tests
[xUnit.net 00:00:00.28]   Discovered:  Controls.TestCases.WinUI.Tests
No test matches the given testcase filter `Issue27563` in D:\a\1\s\artifacts\bin\Controls.TestCases.WinUI.Tests\Debug\net10.0\Controls.TestCases.WinUI.Tests.dll

⚠️ Issues found

• ❌ Issue27563 FAILED with fix (should pass)

📁 Fix files reverted (2 files)

• eng/pipelines/ci-copilot.yml
• src/Controls/src/Core/Handlers/Items/CarouselViewHandler.Windows.cs

---

[kubaflo]

The test is failing :/