Xamarin.Forms Android SfChart - System.ArgumentException: Not a legal OleAut date when AOT on Cortex-a53 devices

[Anthony Ramirez]

Hi!

This bug was difficult to track down as it only happens on some Android devices. 

SfChart will throw a System.ArgumentException: Not a legal OleAut date exception, when the following is true:

• AOT Android app
• ABI = armeabi-v7a
  
• Running Android on a Cortex-A53 device. Any of these devices https://www.gsmarena.com/results.php3?sChipset=11,40,14,64 There are more like Nexus 5X which has multiple modes
• SfChart is displayed (even before data is loaded)

Attached is a sample app that has AOT enabled. 

IE the following settings in csproj for Release configuration

AotAssemblies = true

EnableLLVM=true

BundleAssemblies=true

If you run it on one of the devices above the error will occur. If you run using Debug configuration, or update Release config and disable AOT, the error does not occur.

It appears that Startup Tracing with a Custom Profile resolves my issue, as I do not use an SfChart when my app launches, so I will be using that moving forward.

Please let me know if you have any questions.

I also found this post which appears similar https://www.syncfusion.com/forums/155325/sfchart-exception-on-android.

And this update note for Essential Studio for Xamarin.Android https://help.syncfusion.com/xamarin-android/release-notes/v18.2.0.46?type=all

Thanks,

Ant

Attachment: SfChart_AOTError_a5fdd144.zip

[Saravanan Madheswaran]

Hi Anthony, 

 

Greetings from Syncfusion.  

 

Currently we are validating the reported issue at our end, we will update you the complete status on or before 24^th September 2020.  

 

Regards, 

Saravanan.  

[Anthony Ramirez]

Hi Saravanan,

Looks like using Startup Tracing with a Custom Profile may be causing a different issue, so I may need a fix for this after all.

I will know more later today.

Thanks,

Ant

[Saravanan Madheswaran]

Hi Anthony, 

 

We have created a new incident under your Direct trac account to follow up with this query. We suggest you to follow up with the incident for further updates. Please log in using the below link.   

  

https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents/ 

 

Regards, 

Saravanan