We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

Crash on Android when quickly tapping on SfDataGrid

We have a 100% reproducable crash with the SfDataGrid. Is there anyone who had simmilar problems?

Below is the minimal code base that will cause the app to crash when the user taps rapidly with two fingers on the grid (full project attached).

using System;
using Android.App;
using Android.Content;
using Android.Runtime;
using Android.Views;
using Android.Widget;
using Android.OS;
using Syncfusion.SfDataGrid;

namespace SfDataGridCrash
    public class Test
        public string T1 { get { return "T1"; } }
        public string T2 { get { return "T2"; } }
        public string T3 { get { return "T3"; } }

    [Activity(Label = "SfDataGridCrash", MainLauncher = true, Icon = "@drawable/icon")]
    public class MainActivity : Activity
        protected override void OnCreate(Bundle bundle)


            LinearLayout layout = FindViewById<LinearLayout>(Resource.Id.MainLayout);
            SfDataGrid grid = new SfDataGrid(BaseContext);
            grid.SourceType = typeof(Test);
            grid.ItemsSource = new Test[] { new Test(), new Test(), new Test() };
            grid.SelectionMode = SelectionMode.Single;

We could reproduce this behaviour on all our Samsung and Getac tablets.
Sometimes it takes 100 taps, but sometimes it happens when the user double clicks an item during the normal use of our app.

Attachment: SfDataGridCrash_7ead70d2.zip

1 Reply

PK Prasanth Karthikeyan Syncfusion Team January 12, 2016 03:24 PM UTC

Hi Denis,

Thanks for using Syncfusion Products.

We were able to reproduce the issue “SfDataGrid crashes when Tapping rapidly with two fingers”. The problem here is when you tap two different rows, while tapping rapidly the grid tries to select both the tapped rows at the same time and hence the grid crashes as this is not possible with single selection as mode. We have fixed this issue internally and the fix for the reported issue will be available in our Volume 4 Service Pack 1 which will be available by the mid of February 2016.

Please let us know if you have any query.



Live Chat Icon For mobile
Up arrow icon