Update: I have also posted this as an incident
We have encountered an issue with SfListView on Android.
In our code, we use the ItemTapped event and during this event perform custom navigation to a different control, which causes the SfListView to be removed from its parent layout. This, in turn, causes an ObjectDisposedException:
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Syncfusion.ListView.XForms.Android.ListViewItemRenderer'.
I have worked around the issue for now by using await Task.Delay(100); which apparently lets the control's renderer do the thing it has to do before it is removed, but it is clearly not an ideal solution and is clearly quite fragile. The same issue occurs when TappedCommand is used instead.
I have uploaded a simple repo demonstrating the problem to my GitHub and also attached a copy of the solution with this post.