Bug 47971 - XF UWP ListView Items no longer display ImageCell is the problem
Summary: XF UWP ListView Items no longer display ImageCell is the problem
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.3
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-11-25 15:52 UTC by Karl Shifflett
Modified: 2016-12-23 12:13 UTC (History)
4 users (show)

See Also:
Is this bug a regression?: ---
Last known good build:


Description Karl Shifflett 2016-11-25 15:52:08 UTC
Using and XF for VS

One of these updates has broken UWP ListView.  The items no longer display.  Last week the same simple app worked using UWP.

Items display in iOS and Android, but not UWP.

Microsoft, you need much better quality control and testing.

Real simple XAML from the Xamarin Dev Days hands on lab.

    SelectedItem="{Binding Path=SelectedSpeaker, Mode=TwoWay}"
    ItemsSource="{Binding Path=Speakers}">
                Command="{Binding Path=BindingContext.SpeakerSelectedCommand, Source={x:Reference ListViewSpeakers}}"
                Text="{Binding Path=Name}"
                Detail="{Binding Path=Title}"
                ImageSource="{Binding Path=Avatar}" />
Comment 1 Karl Shifflett 2016-11-25 21:46:42 UTC
Found the problem.

The ImageCell is the issue.

ImageCell is broken for UWP ListView.

Verified on multiple projects.

Comment 2 E.Z. Hart [MSFT] 2016-11-29 05:31:32 UTC
The issue is not with the ImageCell. It's a problem with the Command's CanExecute method and the binding of Command, CommandParameter, and an issue with the DataTemplate temporarily inheriting the binding context of the ListView. 

I've submitted a PR: https://github.com/xamarin/Xamarin.Forms/pull/572
Comment 3 Samantha Houts [MSFT] 2016-12-02 00:41:31 UTC
Should be fixed in 2.3.3-SR1. Thank you!
Comment 4 Parmendra Kumar 2016-12-23 12:13:59 UTC
I have checked this issue with Xamarin.Forms and followed sample code provided in bug description and I am no longer able to reproduce this issue.

Hence closing this issue.

Note You need to log in before you can comment on or make changes to this bug.