On Android, when grouping with IsItemSwipeEnabled=True, the Group Header is accidentally swipe-able and reveals the ItemSwipeContent.

The issue is presenting on Android, but not iOS (UWP unknown)

v 2017.2.818.234

When you have placed the ListView within a StackLayout and the number of items is greater than what the screen can fit, the following undesired effects are observed:

in Android: The last item is cut off 

in iOS: You are not able to scroll down the list and it always bounces back to the original view

When you have enabled multiple selection of the RadListView and are using the LoadOnDemand manual functionality, a check box appears on the "Load More" item as well.

Available in the R3 2017 SP release.

Currently the SelectedItems collection does not support two way binding. Expose API to support two way binding.

Introduce ability to programmatically begin a cell swipe to reveal the SwipeContentTemplate. 

An example use case: tapping a vertical ellipsis button (context menu style) in cell template.

In multiple selection scenarios with ItemSwipeContent when the item is swiped, the selection indicator hides the content of the list item.

When setting LineSeries StrokeThickness value in the PCL project (XAML or code-behind), it is not respected at runtime in the iOS project.

For now, the workaround is to use a custom renderer to reset the TKLineSeries's Palette with a new  TKPaletteItem containing a TKStroke with the preferred thickness value.

In a scenario where the RadListView is added to and removed from the visual tree multiple times, a memory leak occurs and the gref count always increases. 

You can reproduce the issue with the SDK example http://docs.telerik.com/devtools/xamarin/controls/listview/gestures/listview-gestures-cell-swipe.

In UWP everything looks fine, but in Android both labels of the item swipe template appears.

Available in minor release 2017.2.0818. It will also be available in the R3 2017 release.

The first one is with action Reset and it is not expected. Note that this cannot be reproduced with Multiple selection.

Available in the 2018 R2 SP release.

Reproducible on Android 6.0  or higher.

When you have set a group header template to the ListView and you rotate the Android device from Portrait to Landscape, the group headers that fail within the visible field are cut off.

Edit: Avalable in R3 2017 SP release.

The grouping does not work in Android if you do not use simple type properties to group the items. In UWP everything works fine, in iOS I have not tested the scenario. I added a demo solution to test the issue.

Available in the R2 2018 release.

Provide API which enables the group headers to remain in the view when scrolling until the next ones push them away.

Add support for header and footer that scroll with the content of the list view.

Example:
<telerikListView:ListViewItemStyle BackgroundColor="{DynamicResource MedLightGrey}" BorderColor="{DynamicResource LightGrey}" BorderWidth="1" BorderLocation="Bottom"/>

Available in the R2 2017 PS release

On Android the header items are taking too much space and are invisible using GroupHeaderTemplate.

Available in minor release 2017.2.0602. It will also be available in the R2 2017 SP release.