SfChart Exception on iOS

[Radoslaw Kubas]

Hello,

I noticed in logs SfChart exception on iOS device. It seems to be similar to previous already solved exception problem on Android but details are different. 

System.ArgumentException:  Not a legal OleAut date.

  at System.DateTime.DoubleDateToTicks (System.Double value) <0x104a303a0 + 0x00060> in <85a0be741dba4068b8b83c4563af7fa8#00ab3adb641eb7e0823eab034d032012>:0 

  at System.DateTime.FromOADate (System.Double d) <0x104a30ab0 + 0x00013> in <85a0be741dba4068b8b83c4563af7fa8#00ab3adb641eb7e0823eab034d032012>:0 

  at Syncfusion.SfChart.iOS.SFChartStripLine.UpdateStripLine () <0x107121c80 + 0x00237> in <9a093aaf0cf74a97819fe711b4bb8848#00ab3adb641eb7e0823eab034d032012>:0 

  at Syncfusion.SfChart.iOS.SFChart.UpdateStripLines () <0x107040b50 + 0x000af> in <9a093aaf0cf74a97819fe711b4bb8848#00ab3adb641eb7e0823eab034d032012>:0 

  at Syncfusion.SfChart.iOS.SFChart.UpdateChart () <0x10703ac00 + 0x021b3> in <9a093aaf0cf74a97819fe711b4bb8848#00ab3adb641eb7e0823eab034d032012>:0 

  at Syncfusion.SfChart.iOS.SFChart.LayoutSubviews () <0x10703abd0 + 0x0001b> in <9a093aaf0cf74a97819fe711b4bb8848#00ab3adb641eb7e0823eab034d032012>:0 

  at (wrapper managed

It was 100% repeatable but seems to be dependent on data series because when I created new random data series exception disappears. Could you check it on your site and fix if possible? 

Best regards,

Radek

[Yuvaraj Palanisamy]

Hi Radoslaw Kubas, 

 

Greetings from Syncfusion. 

 

We have analyzed your query and we have fixed the issue in assumption based on the stack trace. And now we are in testing phase to ensure its stability. Hence, we will provide the patch on or before Oct 27, 2020. 

 

Regards, 

Yuvaraj 

[Yuvaraj Palanisamy]

Hi Radoslaw Kubas,  

   

Thanks for your patience.  

   

Based on the stack trace report, we have fixed the reported crash issue in iOS and we have generated the patch for this fix.  

Please find the patch details form below.  

   

Please find the patch from the below link: http://syncfusion.com/Installs/support/patch/18.3.0.35/999661/F159000/SyncfusionPatch_18.3.0.35_999661_10262020113231142_F159000.exe  

   

Please find the patch assemblies alone from the below location:   

http://syncfusion.com/Installs/support/patch/18.3.0.35/999661/F159000/SyncfusionPatch_18.3.0.35_999661_10262020113231142_F159000.zip  

   

Please find the NuGet from the below location:   

http://syncfusion.com/Installs/support/patch/18.3.0.35/999661/F159000/SyncfusionNuget_18.3.0.35_999661_10262020113231142_F159000.zip  

   

Assembly Version: 18.3.0.35  

      

Disclaimer:    

   

Please note that we have created this patch for version 18.3.0.35 specifically to resolve the issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.  

   

NOTE: We don’t have provision to generate a patch for weekly NuGet versions. So, we have generated this patch in the main release version.   

   

   

Please clear the NuGet cache, before using the latest one.
https://www.syncfusion.com/kb/6987/how-to-clear-nuget-cache    

   

   

Please check and let us know whether the reported problem has been resolved or not. Based on your confirmation, we will check the possibility to include this fix in our upcoming official release.  

 

Regards, 

Yuvaraj