When you try to swipe several items at once by using more than 1 finger - the items are stuck and the space where the ItemSwipe content should be present is left blank. The issue can also be observed if you swipe items very fast. 

This can be reproduced in the SDK examples ->ListView -> Gestures -> CellSwipeEvents. 
1. Change the content of the items so that they have uneven height
2. Scroll down 
3. Delete an item by swiping
-> Expected result : The items re-arrange correctly
-> Actual result : The item is deleted but the ListView is scrolled up when the UI is updated

When LoadOnDemand event have loaded its data then there is some kind of jumping down through the new items while scrolling. 

When the ListView has more items, it could be vertically scrolled, however, there is no UI for vertical scrollbar on Android.  The same can be observed with RadTreeView control.

If EndItemSwipe() is called inside the ItemSwiping event handler, the ItemSwiping event continues to occur on iOS until the user physically ends the swipe gesture.

Flickering occurs after the RadListView is refreshed. The issue is observed with v 2019.1.116.1 of Telerik UI for Xamarin.

I have a listview with item templates in a modal popup but it is not visible on iOS simulator. On Android device it is OK.

Java.Lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first.

For example change the IsPullToRefreshEnabled state on button click, when button is pressed several times, exception is throw.

Follow this tutorial https://docs.telerik.com/devtools/xamarin/controls/listview/listview-features-load-on-demand#loading-mode-with-collection 

It works on Android and iOS, but on UWP it is defaulting to Explicit mode and clicking the load button crashes the app.

When RadListView is setup to load its items on demand and the LayoutDefinition is GridLayout with SpanCount set to 2 or more, the Footer Template does not take all the width, it expands only to the Width of the first column.

Currently groupheader can be stretched by using GroupHeaderLength property instead rather than resolving it automatically.

The following exception is thrown when scrolling ListView with Grid layout with many columns and rows:
Windows.UI.Xaml.LayoutCycleException: Layout cycle detected.  Layout could not complete.

The bug can be reproduced on iOS 13 only. It is not reproducible on earlier versions of iOS. Run the attached project on iOS 13 device or Simulator to reproduce it.

Sometimes when focusing an entry and the onscreen keyboard shows up, the ListView is not scrolled correctly, so the entry is overlapped by the keyboard. The ListView layout appears messed up after that and the scrolling does not behave correctly.

Cell height is not being adjusted to show all the content. the text overflow and it overlap the cell below. It seems that dynamic size is not respected.

if the swipe content of the cells are buttons, dragging the buttons up and down will keep the swiped cells in the same position of the screen, creating unexpected animations and showing the entire swipe content of the cell.

When swiping a cell, the swipe content of the cell will be shown if the swipe threshold is reached.  On iOS, the swipe content of another cell can be shown immediately by swiping another cell (which is an expected behaviour).  However on Android, when the user swipes another cell, the swipe content of the other cell isn't shown (while the swipe content of the first cell becomes hidden).  The user has to swipe the other cell again to show the swipe content.

GroupHeaderTemplate has a default gray background applied and setting Transparent does not take any effect.

When any control (Frame, for example) with applied Margin is placed inside GroupHeaderTemplate of the ListView, the Margin value is not respected on iOS.

Hi,

I rolled my app with the ListView out to production and are getting 8+ crashes a day from 140 users with the above issue. I have included a stack trace. I cannot find the steps to reproduce the issue in development. I have rolled back to using the native ListView as this does not crash the app.

Attached is an example project to see what I am doing in general terms, but I have not been able to reproduce this crash in it.

My guess is that a DataTemplate is not being cleaned up properly and when the data behind is changed it attempts to access the control that represented the data in the DataTemplate.

Regards
Anthony