Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 60371 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Created attachment 25448 [details]
Solution Example for Grouping Sample Bug
In iOS 11, we are seeing that frequently when removing items from a group that a group header duplicates. We do not see this behavior in iOS 10.
It doesn't happen every time but with the attached sample, I'm able to recreate about 1/2 the time by:
- removing some items from the list midway through the list
- then scrolling down near the bottom of the list and removing one or 2 items from the last grouping
- then removing items from the 2nd to the last grouping until all items are gone from the group
- removing more group's items continues to duplicate the the group header
To remove items from the list in the sample application, just click the item row to exercise the ItemSelected event which will do a delete of the item in the group.
private void lstView_ItemSelected(object sender, SelectedItemChangedEventArgs e)
var item = (VeggieModel)((ListView)sender).SelectedItem;
var group = grouped.Where(g => g.Contains(item)).FirstOrDefault();
Created attachment 25449 [details]
Image showing duplicated group headers
It seems like I could get it to do what you described on iOS 11 so I'll set this as confirmed until we can get it looked into further.