/azp run

Thank you for the suggestion, @jsuarezruiz.

I could write a test similar to what you described, but I believe it wouldn’t accurately represent the issue I’m trying to address.

The line below invokes the MapSource method directly without raising a PropertyChanged event for the Source property:

Since MapSource is triggered as part of the handler setup, and not through a change to Image.Source, subscribing to PropertyChanged and checking for Image.Source won’t capture that UpdateValue() call.

To replicate the issue in the Sandbox app, follow the steps below:

1. Add Image to Resources

Add shopping_cart.png to the Resources/Raw folder.

2. Define UI in MainPage.xaml

<VerticalStackLayout Margin="20" x:Name="stack">
    <Button AutomationId="MauiImage" Text="To Local Storage" Clicked="Button_Clicked"/>
    <Button AutomationId="MauiImage1" Text="Load Images" Clicked="Button_Clicked1"/>
    
    <CollectionView x:Name="cauroselView">
        <CollectionView.ItemsLayout>
            <LinearItemsLayout Orientation="Horizontal" />
        </CollectionView.ItemsLayout>
        <CollectionView.ItemTemplate>
            <DataTemplate>
                <Image WidthRequest="300" Source="{Binding .}" />
            </DataTemplate>
        </CollectionView.ItemTemplate>
    </CollectionView>
</VerticalStackLayout>

3. Add Code-Behind in MainPage.xaml.cs

public partial class MainPage : ContentPage
{
    public MainPage()
    {
        InitializeComponent();
        Images = new List<string>();
    }

    public List<string> Images { get; set; }

    private async void Button_Clicked(object sender, EventArgs e)
    {
        for (int i = 0; i < 25; i++)
        {
            var resourceStream = await FileSystem.OpenAppPackageFileAsync("shopping_cart.png");
            var path = Path.Combine(FileSystem.AppDataDirectory, $"temp{i}.png");

            if (File.Exists(path))
                File.Delete(path);

            using (var fileStream = File.Create(path))
            {
                await resourceStream.CopyToAsync(fileStream);
                Images.Add(path);
            }
        }
    }

    private void Button_Clicked1(object sender, EventArgs e)
    {
        cauroselView.ItemsSource = Images;
    }
}

4. Set Breakpoint

Place a breakpoint at the following line in ImageHandler.Android.cs:

5. Test the Behavior

• Run the app.
• Click "To Local Storage" to generate and save image files locally.
• Click "Load Images" to bind the list of image paths to the CollectionView.
• Scroll through the CollectionView.

Without the PR changes:

• The UpdateValue() method will be invoked multiple times while scrolling.
• This is unintended and incorrect behavior.

With the PR changes:

• The UpdateValue() method will not be invoked during scrolling.

Images inside a CollectionView or CarouselView are causing lot of issues for us. Laggy scroll, poor performance... This seems like it will help improve on that. @rmarinho @PureWeen Could you take a look at this?

This can also explain my degradating performance in my CV's with local images