[Bug] CollectionView iOS draws both EmptyView and Items/ItemTemplate

[RemcoDEV]

Description

CollectionView iOS draws both EmptyView and Items/ItemTemplate. The itemtemplate UI becomes unresponsive, because the emptyview is drawn over it.

Steps to Reproduce

1. Create a collectionview with an itemtemplate and an emptyview.
2. Fill the collectionview in the viewmodel and call onpropertychanged on the itemssource binding.
3. Sometimes (~3 out of 5 times) the collectionview displays both the emptyview and the itemtemplates.

Expected Behavior

Only draw the emptyview when the itemssource is empty.

Actual Behavior

Both the emptyview and the items/itemtemplates are drawn.

Basic Information

• Version with issue: release-5.0.0-sr3.1
• Last known good version: release-5.0.0-sr2
• Platform Target Frameworks:
  • iOS: 14.3
  • Android: Works fine on android
  • UWP: --
• Android Support Library / AndroidX Version: --
• NuGet Packages:
• Affected Devices: tablets, phones

Environment

Visual Studio 2019 / Windows 10

Build Logs

--

Screenshots

'Nothing to display' is the emptyview.
This example is a grouped collectionview, but it also happens to non-grouped collectionviews.

Reproduction Link

--

Workaround

Reconstructing the page sometimes works.
Refreshing does not work. Something definitely goes wrong when constructing the page.

[hartez]

@RemcoDEV Can you post a small reproduction project? Or at least paste in an example of your ItemTemplate, EmptyView, and the code you're using to set up your ItemsSource?

[lewinzki]

@RemcoDEV I encounter the same bug. A possible workaround is to add IsVisible to the content of your EmptyView. E.g. <StackLayout IsVisible="{Binding DocumentGroups, Converter={StaticResource ListIsNullOrEmptyConverter}}">. Here I have used the converter ListIsNullOrEmptyConverter from the XamarinCommunityToolkit. The converter is also easy to implement yourself if you don't want the dependency.

@hartez If it is any help I can report that this bug only occurs when the CollectionView is a child of a TabbedPage.

[decv86]

@RemcoDEV I encounter the same bug. A possible workaround is to add IsVisible to the content of your EmptyView. E.g. <StackLayout IsVisible="{Binding DocumentGroups, Converter={StaticResource ListIsNullOrEmptyConverter}}">. Here I have used the converter ListIsNullOrEmptyConverter from the XamarinCommunityToolkit. The converter is also easy to implement yourself if you don't want the dependency.

@hartez If it is any help I can report that this bug only occurs when the CollectionView is a child of a TabbedPage.

Tnx man!

[Deepfreezed]

Same issue for me. Draws both Empty and Item View. Not using Tabbed Page. Xamarin test team should really use rest service to test with some async calls. I am sure all this works when you have data hardcoded into the view model.

Just updated to 5.0.0.2012 from 5.0.0.1931. There are other issue in 5.0.0.1931 that breaks CollectionView binding when visibility state is initially false. At least that seems to be fixed in 5.0.0.2012.

[rmarinho]

Hello all, can someone please upload a small reproduction of this issue so we can investigate it further?!

thanks.

[marcojak]

Same problem here.

[Redth]

@marcojak can you please upload a small reproduction of the issue?

[beeradmoore]

@hartez @rmarinho @Redth , I have added a small repro project. There is some gross code incoming so brace yourselves.

In this particular case I was able to replicate it by doing what I do in my prod app, which took me down a rabbit hold where I found some jank code. Fixing my jank fixes the issue, however I think the underlying issue may still happen in other circumstances.

Problem is only present when for me CollectionView is inside a CarouselView. If I replace the CarouselView with a CollectionView the problem goes away. The other bit of jank in the code is I am creating an ObservableCollection on my MainPage which is populated by loading a local file/web request/etc, and a reference of this is passed to MyCollectionView class.

Within MyCollectionView I keep a reference of the ObservableCollection (Data = data;) AFTER I set the BindingContext.

My workaround is to fix the jank and move this line to before I set the BindingContext and then the problem goes away. Another possible solution I havn't tried would be setting ItemsSource of MyCollectionView from the MainPage.

EmptyCollectionViewBug.zip

So yeah, there is some things here that I shouldn't be doing, but its still putting CollectionView in an odd state where it both has and does not have data.