Hello, in the GitHub thread you mention the following:
Also, if we used the below code for macOS then it works fine in XF 5 but not in XF 4.8 or below.
this.ScrollOwner.ScrollToAsync( 0, 0, false);
Could you provide in this thread a nuget package with this "solution" that you comment on GitHub? at least to have a temporary fix until this is officially fixed? at least for those of us who face this error in Xamarin.Forms 5 in order to have a solution even though we have to be anchored in this nuget that you provide. I wait your answer.
Hi, thanks for the quick response, I attach the versions that I use:
Xamarin.Forms 5.0.0.2083
Syncfusion.Xamarin.SfListView 19.2.0.59
Syncfusion.Xamarin.GridCommon 19.2.0.59
Syncfusion.Xamarin.DataSource 19.2.0.59
Syncfusion.Xamarin.Core 19.2.0.59
Syncfusion.Licensing 19.2.0.59
Hello, I inform you that you have received an official response from the Xamarin.Forms team in the GitHub thread indicating the cause of the problem and indicating that the solution should be applied from the Syncfusion team:
Xamarin.Forms team response:
In #12721 we removed a variable from how the scroll position was determined. I think this fix was the right one, the problem we are seeing right now is that basically you on your side @saiganeshls2504 have implemented a workaround for our code that wasn't working correctly.
I don't see any way to fix this on our side without reintroducing the original bug or break other functionality. For instance, I came up with this that should fix your scenario, however, if someone tries to scroll to the bottom using this, we will now break them.
The only option I see, which is not desirable, is to add some new property to restore the legacy code and add that back. Do you have any options on your side? Like fix this code on your side and make the minimum dependency on Forms the version with this fix?
Thank you very much, with the custom assemblies that you have provided the problem has already been solved, I will stay on this version until there is an official solution published. Greetings.
I'm getting this issue on Xamarin Forms Ios
Using
Xamarin Forms 5.0.0.2337
SfListView 19.4.0.47
Is it the same problem?
I'm facing the same problem on iOS
Xamarin Forms 5.0.0.2337
SfListView 19.4.0.50
Hello, I'm seeing similar issues but not on all lists. Very strange.
I have a Main form (no list) then a child form (with list). Selecting an item navigates to a grandchild form (with another list).
Child form list populates but all items disappear when the code exits the OnAppearing() method of the Form.
Grandchild form list populates and displays, no problem. Identical code, data different.
protected async override void OnAppearing()
{
base.OnAppearing();
await viewModel.LoadCategories();
Title = "Catalogue";
ForceLayout(); //the list is populated and visible when hitting a break on this line
} //the list disappears after exiting this method. No other code of ours runs
No code change. This was working prior to most recent XF update and Syncfusion controls update.
We tried this:
Loading data in both the form constructor after BindingContext set AND in the OnAppearing() method as shown above
If we do not fetch data in the form constructor, the list does not appear.
If we don't fetch data in the OnAppearing() method, the list does not appear.
But the data is there when checking the return in either fetch.
We have to fetch data twice - in form constructor AND OnAppearing() method.
If we get data twice as described, the items appear but the list is set to bottom of screen, as if LayoutOptions.End is set but that is actually set to FillAndExpand in xaml.
Very strange behavior.
We will await the Syncfusion update on March 1st., else rollback to XF 4.8 etc.
Thanks Lakshmi, I thought this was all related...
I rolled back to XF 4.8, removed the extra data fetch I added in the VM constructor and all is working well again.
I'll keep monitoring Syncfusion updates and try when they're ready.