Group header dissapearing on ios

Question

Hello,I have a problem with group headers on iOS.i have a page with a maui carouselview.In the carousel i have 3 views, each view contains a different SfListView with groupingOn initial display i can see the group header on view1.When i swipe to view2, i can see the group headers on this view3.When i swipe to view3, i can see briefly the group headers in view3, but then the group headers dissapear.When i swipe back to view2 the groupheaders have dissapeared here too. Also on view1.On Android all works fine.Micrososft.Maui 9.0.30Syncfusion.Maui 28.1.39

Sowntharya Jayamoorthy · Accepted Answer

Hi Dirk Wilhelm,

We sincerely apologize for any inconvenience you have experienced. After thoroughly analyzing the CarouselView workflow, we discovered that when swiping, the BindingContext of a CarouselViewItem is changed. This process results in the resetting of the ListView’s ItemsSource, which by default, clears the group descriptors.

To maintain your desired groups when the ItemsSource changes, you will need to re-add the groups programmatically. This behavior is inherent to the current grouping feature of the ListView. Unfortunately, we are unable to modify this behavior in the source, as it may impact the default functionality of the grouping feature.

Additionally, you can refer to the following UG link for more details on grouping and its limitations in SfListView : https://help.syncfusion.com/maui/listview/grouping

We kindly request you to use below workaround to resolve the reported issue at your end.

Code snippet:

<CarouselView.ItemTemplate>

<Grid>

<syncfusion:SfListView x:Name="listview" ItemsSource="{Binding GroupedData}"

BindingContextChanged="listview_BindingContextChanged">

---------------------------------------------------

</ syncfusion:SfListView>

</DataTemplate>

</CarouselView.ItemTemplate>

</CarouselView>

private void listview_BindingContextChanged(object sender, EventArgs e)

{

var list = (sender as SfListView);

if(list!.DataSource!.GroupDescriptors.Count == 0)

{

list!.DataSource!.GroupDescriptors.Add(new GroupDescriptor()

{

PropertyName = "Category",

});

}

Regards,
Sowntharya J

Anees Fathima Shajahan · Answer

Hi Dirk Wihlem,Using the .NET MAUI Carousel in a MAUI app on iOS results in a crash. We are in the process of preparing a sample to replicate the reported issue and will share an update by January 17, 2025.Regards,Anees Fathima.

Anees Fathima Shajahan · Answer

Hi Dirk Wihlem,We have prepared sample and review the reported scenario and were able to reproduce the issue "The ListView group headers within a CarouselView are not visible on iOS, when swiping between views". We have logged a bug for this issue and fix will be included in our upcoming NuGet release, which is planned to roll out on February 4, 2025. We appreciate your patience until then. You can track the status of the issue in the feedback report below.Feedback link:  https://www.syncfusion.com/feedback/64743/listview-groupheader-not-visible-in-carouselviewRegards,Anees Fathima.

Anees Fathima Shajahan · Answer

Hi Dirk Wihlem,We apologize for the inconvenience caused.We are unable to
include the fix for this issue in this week's NuGet release. However, we will
include the fix in our upcoming NuGet release, scheduled for rollout on
February 18, 2025. We greatly appreciate your patience until then.Regards,Anees Fathima.

Anees Fathima Shajahan · Answer

Hi Dirk Wihlem,We have attached a custom package with a fix for this issue. Please confirm whether the issue has been resolved on your side.Note: Before installing the custom NuGet package, we recommend uninstall the Syncfusion packages from your application and clearing the NuGet cache.How to install the MAUI custom NuGet in the Windows machine?How to clear NuGet cache?Regards,Anees Fathima.Attachment: Syncfusion.Maui.ListView.28.2.4_d84cce72.zip

Dirk Wilhelm · Answer

Hello,thank you very much for this custom package.I can confirm that this package fixes the problem.Regards,  Dirk Wilhelm

Anees Fathima Shajahan · Answer

Hi Dirk Wilhelm,We're pleased to hear that the custom package we provided has resolved the issue. As previously mentioned, this fix will be included in our upcoming NuGet release, scheduled for rollout on February 18, 2025. We sincerely appreciate your patience until then.Regards,Anees Fathima.