1. Home
  2. Forum
  3. Xamarin.Forms
  4. Windows IOT Enterprise - Small Footprint device - Touch Crashes

Windows IOT Enterprise - Small Footprint device - Touch Crashes

Touching the screen that has a SFDataGrid - occassionaly triggers a crash.

No events are firing in the csharp code at the time of the crash.  

Screen is a StackLayout , StackLayout has 4 children each with a datagrid

Only one of the 4 children is visible at a given time navigation to each one via  a button - button only changes visibility - no loading etc.

Gird loads and funciton but occassionaly a touch of the screen  triggers the following error 

Exception Info: System.NullReferenceException
   at Syncfusion.SfDataGrid.XForms.WPF.SfDataGridControlRenderer.SfDataGridControlRendererPreviewTouchMove(System.Object, System.Windows.Input.TouchEventArgs)
   at System.Windows.Input.TouchEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Input.TouchDevice.RaiseTouchMove()
   at System.Windows.Input.TouchDevice.ReportMove()

Error trapping is caught, logged and handled throughout the process - when the above occurs it does not fall into a catch at any place in the app.


Version SFDataGrid 19.3.0.43

OS:  Windows IOT Enterprise os build 19044.1645 Version 21H2   

Trying to avoid moving to a newer version of SFDataGrid at this point in the life cycle because of retesting that would be required.  Any ideas suggestions greatly appreciated 





4 Replies
SV Suja Venkatesan Syncfusion Team April 28, 2022 02:01 PM UTC

Hi David,


We would like to let you know that we are unable to replicate the reported issue on our end. However, based on the provided stack trace we have added possible null checks and generated new custom assemblies from a private build, which you can download from here,


The assemblies should be replaced with the existing assemblies in the following location.                                

{Syncfusion Installed location}\Essential Studio\19.3.0.43\Xamarin\lib\pcl\Syncfusion.SfDataGrid.XForms.dll                                           

{Syncfusion Installed location}\Essential Studio\19.3.0.43\Xamarin\lib\uwp\Syncfusion.SfDataGrid.XForms.dll                                        

{Syncfusion Installed location}\Essential Studio\19.3.0.43\Xamarin\lib\uwp\Syncfusion.SfDataGrid.XForms.WPF.dll                                 


Please refer the following documentation link for applying custom assembly. 

KB link: https://www.syncfusion.com/kb/8279/how-to-apply-the-custom-assemblies-when-configured-the-project-with-syncfusion-nuget 


Disclaimer : Please note that we have created these assemblies for the version 19.3.0.43 and Xamarin.Forms version 5.0.0.2012 specifically to resolve the reported issue in this forum. Could you please check with the above assemblies which resolves the reported issue?   


Regards,

Suja


Attachment: Custom_DLL_1b9d67e0.zip

DF David Feltz April 28, 2022 07:58 PM UTC

First and foremost - thanks for the quickly reply and the custom dll you provided.

We created a build of the application with these new Custom DLLs and there was a change in behavior.  The error trapping that was in placed was triggered and our app was able to enter into a recovery mode without crashing.  

Our current plans call are to use these "custom" dlls as part of a demonstration application for a very large client that will move into a pilot program very soon.  While we will conduct a robust amount of testing, is there any obvious reasons we can't use these in a production application.

Separately from this test, we also spun off a version of the application and updated to version 20.1.0.47 and were still able to create the issue.  Our plans were to potentially move to the newer/current version of the SFDataGrid as part of our next version of our application which is anticipated to move into integrated testing in the next few weeks.  If you can advise when this change is made part of the current version, it would be appreciated.





SV Suja Venkatesan Syncfusion Team April 29, 2022 01:33 PM UTC

Hi David,


We will include this fix in our upcoming weekly NuGet which is scheduled on May 3,2022. We will let you know once it is released with the fix. We appreciate your patience until then.


Regards,

Suja 



SV Suja Venkatesan Syncfusion Team May 3, 2022 01:49 PM UTC

Hi David, 


We have included the fix for the issue “System.NullReferenceException while touching the screen that has a SFDataGrid ” in our latest Weekly Nuget release update version 20.1.0.52 which is available for download  (https://www.nuget.org/).    


We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance. 


Regards,  

Suja 


Loader.
Up arrow icon