[WinAppSDK] Visual Tree stores wrong outdated Items

[AuderixDev]

Current behavior

Working with Listview and ListView.ItemTemplate I noticed a strange behaviour on some CommandParameters.
I debugged it with the Visual Tree Viewer and noticed, that after removing items from the Listview, some items are reappearing.
Further interactions with the ListView leads to wrong CommandParameters.

Not tested on other platforms!

Expected behavior

The Visual Tree should represent the underlaying data.

How to reproduce it (as minimally and precisely as possible)

MainPage.xaml

...
 <ListView ItemsSource="{Binding NameList}" x:Name="outerList">
   <ListView.ItemTemplate>
     <DataTemplate>
       <StackPanel Orientation="Horizontal" x:Name="innerobject">
         <TextBlock Text="{Binding Id}" />
         <Button Content="Remove"
                 Command="{Binding DataContext.RemoveMe, ElementName=outerList}"
                 CommandParameter="{Binding Id}"/>

       </StackPanel>
       
     </DataTemplate>
    </ListView.ItemTemplate>
 </ListView>
...

MainModel.cs

...
  public IListState<Customer> NameList => ListState<Customer>.Empty(this);

  public async Task AddToList()
  {
      await NameList.AddAsync(new Customer());
  }

  public async Task RemoveMe(Guid id)
  {
      await NameList.RemoveAllAsync(match: x => x.Id == id);
  }

  public partial record Customer()
  {
      public Guid Id { get; } = Guid.NewGuid();
  }
...

Minimal Project: UnoApp14.zip
(Startup Project. WinAppSDK Unpacked)

Workaround

No response

Works on UWP/WinUI

No

Environment

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

No response

Affected platforms

Windows (WinAppSDK)

IDE

Visual Studio 2022

IDE version

17.11.5

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

Thanks for the report! We're not managing the implementation of TreeView when running on WinAppSDK, though we're pulling the source from the official implementation into Uno.

It would be best to open this issue in the WinUI repository, once it's fixed there we can import it into Uno.