In the Xamarin.Forms documentation at https://developer.xamarin.com/api/member/Xamarin.Forms.ListView.ScrollTo/p/System.Object/Xamarin.Forms.ScrollToPosition/System.Boolean/
ArgumentException position contains an invalid value for ScrollToPosition.
Whilst this exception is thrown on Android, it is not thrown on UWP, giving the impression that things are working even though there is an issue in the application code. The UWP implementation should throw the exception as per the documentation.
This is using Xamarin.Forms 188.8.131.52
To reproduce, just pass a duff value for the first argument in
public Void ScrollTo (Object item, ScrollToPosition position, Boolean animated)
Confirmed still occurring in 184.108.40.206.
Should be fixed in 2.3.5-pre1
Have verified the bug with latest forms build version 220.127.116.116-pre6.
Issue is seems to be reproducible with latest build as well.
Attaching the logs files , Screencast & the sample created for more Info.
Screencast : https://www.screencast.com/t/50Xzqk4ljWQ
Build Info: https://gist.github.com/GLjackyvaswani/600433ce6f3b92544b42d0392001d326
Created attachment 23486 [details]
Sample project File
As the project size is large, have attached the files changed.
Created Sample forms app, Change the MainPage.xaml & .cs file with the code attached.
Created attachment 23487 [details]
Created attachment 23569 [details]
I am attaching a complete repro project that I tested with. I was able to reproduce the crash on Android when using Forms 18.104.22.168. However the crash no longer occurs when using Forms 2.3.5-pre6.
Just to clarify, we have aligned the behavior on all platforms to be that there is _not_ a crash in this scenario. This means that the docs still require an update to reflect this change.
Verified on xamarin.form version 22.214.171.1246-pre6 using attached sample,issue is not reproduce which was there on xamarin.form version 126.96.36.199.Hence marking it as verified
ScreenCast link : https://www.screencast.com/t/2juWssRY80iC
Notice (2018-05-21): bugzilla.xamarin.com will be
switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.
Please join us on
Visual Studio Developer Community and
GitHub to continue tracking
issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs and copy them to the new
locations as needed for follow-up. The See Also field
on each Bugzilla bug will be updated with a link to its new location
After Bugzilla is read-only, if you have new information to add for a
bug that does not yet have a matching issue on Developer Community or
GitHub, you can create a follow-up issue in the new location. Copy and
paste the title and description from this bug, and then add your new
details. You can get a pre-formatted version of the title and
In special cases you might also want the comments:
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.