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 45206 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 17941 [details]
Just on iOS, on Android works fine.
On a grouped ListView, when add a new item to the group, the ListView scrolls to the top.
To reproduce: run the sample and try to add some items. This will call a function to scroll the list to the last item. Before scrolling, the list will go to the top and then will go to the last item.
I'm using Xamarin 220.127.116.113
Fixed on master.
Created attachment 19339 [details]
update repro project
I am still able to reproduce the issue described when using Forms 18.104.22.168.
This looks related to bug #28277 which describes a similar behavior but has been fixed. However the difference between this case and bug #28277 is that this project uses a grouped collection so the issue seems to still exist when using istView.IsGroupingEnabled = true and ScrollTo (item, group, position, animated)
I tested with a non-grouped ListView and did not experience the issue. However when using a grouped collection and ListView.IsGroupingEnabled = true then the ListView would jump to the top then scroll to the bottom. I've attached a newer repro project to demonstrate this.
The same problem here, Xamarin this will not be fixed, 4 months? that's been hard to work with XF with the quantity of bugs that appear...