1. Home
  2. Forum
  3. Xamarin.Forms
  4. SfChart exception on Android

SfChart exception on Android

Hello,

Recently I noticed strange exception from SfChart. Xamarin.Forms Android release app crashes, iOS version works perfect. The app has TabbedPage with 5 tabs. SfChart is on 5th tab. It’s 100% reproduceable but the problem is that action triggering crash is not connected with SfChart. For example app crashes after admob interstitial ad is displayed and closed on 1st tab (so SfChart is not visible). When you close ad, app crashes with bellow exception )full exception details in attachment).

Thank you for any hint how to fix it!

Best regards,
Radoslaw Kubas

android.runtime.JavaProxyThrowable: System.ArgumentException:  Not a legal OleAut date.
  at System.DateTime.DoubleDateToTicks (System.Double value) <0x904015e0 + 0x0010c> in <6a8dbc65d0194d82b46d77201b49ff62>:0 
  at System.DateTime.FromOADate (System.Double d) <0x90401c1c + 0x00033> in <6a8dbc65d0194d82b46d77201b49ff62>:0 
  at Com.Syncfusion.Charts.DateTimeAxis.GenerateVisibleLabels () <0x8bdd5b6c + 0x001a7> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartAxis.UpdateLabels () <0x8bdd00ac + 0x000fb> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartAxis.ComputeDesiredSize (System.Drawing.SizeF size) <0x8bdcff24 + 0x000c3> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureHorizontalAxis (System.Collections.Generic.List`1[T] axes, System.Drawing.SizeF size) <0x8bde67a4 + 0x000d3> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureAxis (System.Drawing.SizeF size) <0x8bde6340 + 0x0028b> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.Measure (System.Drawing.SizeF availableSize) <0x8bde46a0 + 0x00567> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartBase.MeasureAxis () <0x8bdb9e08 + 0x0012f> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartBase.UpdateArea () [0x00193] in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.ChartBase.OnMeasureChart () <0x8bdb9944 + 0x0007b> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Com.Syncfusion.Charts.SfChart.OnMeasure (System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0x8bdbe724 + 0x001cf> in <c3afc20def9f432bbb3ebb5db9f86d6d>:0 
  at Android.Views.View.n_OnMeasure_II (System.IntPtr jnienv, System.IntPtr native__this, System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0x8ff23554 + 0x00073> in <1725a030f0f74649b5542bd86b23db3d>:0
  at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.64(intptr,intptr,int,int)
--- End of stack trace from previous location where exception was thrown ---





Attachment: exception_f8f2f38b.zip

27 Replies 1 reply marked as answer
RK Radoslaw Kubas June 19, 2020 11:09 AM UTC

I noticed just now that same exception is thrown when app return from background and is resumed. 

RK Radoslaw Kubas June 20, 2020 09:57 PM UTC

I have important update. The exception is thrown only when I use SDK version Xamarin.Android 10.3 (Mono 6.10) . With previous SDK Xamarin.Android 10.2 (Mono 6.8) everything is fine.


AS Anandraj Selvam Syncfusion Team June 22, 2020 12:44 PM UTC

Hi Radoslaw Kubas,  
  
Greetings from the Syncfusion.  
  
Currently we are validating the reported query and we will update the complete details on or before Jun 24, 2020. 
  
We appreciate your patience until then.  
  
Regards, 
Anand Raj S. 


FM Fernando Mendes June 25, 2020 07:13 PM UTC

I'm getting the same error:

Android environment unhandled exception: System.ArgumentException:  Not a legal OleAut date.
  at System.DateTime.DoubleDateToTicks (System.Double value) <0xddb766b8 + 0x0012c> in <1d18bf66c4ff4c4d8428cb5fbf48538f>:0 
  at System.DateTime.FromOADate (System.Double d) <0xddb76d6c + 0x0004b> in <1d18bf66c4ff4c4d8428cb5fbf48538f>:0 
  at Com.Syncfusion.Charts.DateTimeAxis.GenerateVisibleLabels () <0xda3a4ef4 + 0x001b7> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartAxis.UpdateLabels () <0xda39eda4 + 0x00113> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartAxis.ComputeDesiredSize (System.Drawing.SizeF size) <0xda39ebec + 0x000d3> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureHorizontalAxis (System.Collections.Generic.List`1[T] axes, System.Drawing.SizeF size) <0xda3b68dc + 0x000f3> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureAxis (System.Drawing.SizeF size) <0xda3b6444 + 0x002a3> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartCartesianAxisLayout.Measure (System.Drawing.SizeF availableSize) <0xda3b469c + 0x0058f> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartBase.MeasureAxis () <0xda38680c + 0x0013f> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartBase.UpdateArea () [0x00193] in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.ChartBase.OnMeasureChart () <0xda386320 + 0x00093> in <68cb30aa4b664649b219867333d8b509>:0 
  at Com.Syncfusion.Charts.SfChart.OnMeasure (System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xda38b57c + 0x001eb> in <68cb30aa4b664649b219867333d8b509>:0 
  at Android.Views.View.n_OnMeasure_II (System.IntPtr jnienv, System.IntPtr native__this, System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xdd6beb58 + 0x0007f> in :0 
  at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.39(intptr,intptr,int,int)


Please, are there some workaround?

Note: In my case, even using the Xamarin.Android SDK 10.3.1.4, all work fine in several devices, but at least in the Samsung J7 ("Manufacturer": "samsung", "Model": "SM-J700M", "DeviceName": "SM-J700M", "Version": "6.0.1") the bug happens.



DD Devakumar Dhanapoosanam Syncfusion Team June 25, 2020 08:42 PM UTC

Hi Radoslaw Kubas, 
 
We have tried to reproduce the reported issue at our end with the possible cases using the latest chart version and it is working fine at our end. 
 
Can you please share the following details which will be helpful for us to analyze and provide the better solution at earlier? 
·       We have suspected that it may be issue with the provided input range for the DateTimeAxis Minimum or Maximum value. Can you please share the input values set for the DateTimeAxis if possible?  
·       Can you please share the complete chart related code snippet and view model code files if possible? 
·       Can you please share the device model details incase having issue with the specific model or android version? 
·       If possible, can you please modify this simple sample to reproduce the reported issue. 
 
Regards, 
Devakumar D 


FM Fernando Mendes June 26, 2020 01:15 AM UTC

In my case I does not use the Minimum or Maximum axis properties:


    <StackLayout HorizontalOptions="FillAndExpand" VerticalOptions="FillAndExpand" BindingContext="{Binding Statistic}" Padding="0,5,10,0" Spacing="0" AutomationId="stlTrend" x:DataType="vmodels:StudyPageViewModel">
      <Label Text="{exts:Static resx:UILabels.Trend}" FontSize="{StaticResource FontSize10}" FontAttributes="Bold"
              TextColor="{StaticResource secondaryColor}" HorizontalTextAlignment="Center" Style="{StaticResource secondaryMenu}" />
      <chart:SfChart x:Name="chart" 
                     x:DataType="vmodels2:StudyEntryStatisticViewModel"
                     HorizontalOptions="FillAndExpand" VerticalOptions="FillAndExpand"
                     BackgroundColor="{Binding Source={x:Reference studyPage}, Path=BackgroundColor}">

        <chart:SfChart.PrimaryAxis>
          <chart:DateTimeAxis IntervalType="Days" Interval="3" ShowMajorGridLines="false"> <!--RangePadding="None"-->
            <chart:DateTimeAxis.LabelStyle>
              <chart:ChartAxisLabelStyle LabelFormat = "dd/MMM" Font="7" />
            </chart:DateTimeAxis.LabelStyle>
          </chart:DateTimeAxis>
        </chart:SfChart.PrimaryAxis>

        <chart:SfChart.SecondaryAxis>
          <chart:NumericalAxis>
            <chart:NumericalAxis.Title>
              <chart:ChartAxisTitle Text="." TextColor="{Binding Source={x:Reference studyPage}, Path=BackgroundColor}" Font="1" />
            </chart:NumericalAxis.Title>
          </chart:NumericalAxis>
        </chart:SfChart.SecondaryAxis>

        <chart:ColumnSeries
              ItemsSource="{Binding WeekData}"
              XBindingPath="Key" YBindingPath="Value"
              Color="{StaticResource primaryColor}" Width="0.3" />

        <chart:LineSeries
              ItemsSource="{Binding TrendData}"
              XBindingPath="Key" YBindingPath="Value"
              Color="{StaticResource secondaryColor}" />

      </chart:SfChart>
    </StackLayout>

It is important note that the same code running with the same data has a different behavior in different devices, in some works fine and in other happens the error.



DD Devakumar Dhanapoosanam Syncfusion Team June 28, 2020 05:25 PM UTC

Hi Fernando Mendes, 
 
Thanks for your update and chart code snippet. 
 
We need some more time for analyzing the reported issue for the invalid range date time value conversion in our source based on the stack trace details and we will update you further details on June 30, 2020. 
 
Regards, 
Devakumar D 


RK Radoslaw Kubas June 29, 2020 03:07 PM UTC

Hello, sorry for the late reply. In my case, SfChart xaml is as attached. Device I see problems is "Redmi 7A".

Best regards,
Radoslaw Kubas


Attachment: SfChart_f3f4bf6.zip

DD Devakumar Dhanapoosanam Syncfusion Team June 30, 2020 02:43 PM UTC

Hi Radoslaw Kubas/ Fernando Mendes, 
 
Thanks for your update and sharing the chart code snippet. 
 
We have checked the all possible cases for the reported issue and while setting the invalid date time value for the axis Minimum and Maximum only we can reproduce the “Not a legal OleAut date” issue at our end. 
 
 
We will update the bug report details based on the stacktrace on or before July 2, 2020. 
 
Meanwhile if possible, can you please share us the entire chart ViewModel DateTime data value causing this which will be helpful for us to fix the reported issue for your exact scenario. 
 
Regards, 
Devakumar D 


DD Devakumar Dhanapoosanam Syncfusion Team July 2, 2020 12:45 PM UTC

Hi Radoslaw Kubas/ Fernando Mendes, 
 
We have logged a defect report for the reported issue in android. The fix for this issue will be included in our upcoming weekly NuGet release which is expected to be rolled second week of July 2020.  
  
  
If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal link above. 
 
Regards, 
Devakumar D 


RK Radoslaw Kubas July 10, 2020 03:42 PM UTC

I checked with the latest Syncfusion version (18.2.0.44)  and the problem still persists when using SDK version Xamarin.Android 10.3 (Mono 6.10). With previous SDK SDK Xamarin.Android 10.2 (Mono 6.8) it works fine. 

HM Hemalatha Marikumar Syncfusion Team July 13, 2020 12:24 PM UTC

Hi Radoslaw Kubas/ Fernando Mendes, 
 
Sorry for the delay.  
 
Due to some pending testcases, we didn’t include the bug fix in our Volume 2, 2020 release. We have planned to move this fix in our upcoming July 21st weekly NuGet release without having any further delay. 
 
Regards,
Hemalatha M. 


RS Ramya Soundar Rajan Syncfusion Team July 21, 2020 12:22 PM UTC

Hi Radoslaw Kubas/ Fernando Mendes, 
 
We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet. 
 
NuGet Version: 18.2.0.46
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Regards, 
Ramya S 


RK Radoslaw Kubas July 23, 2020 10:21 PM UTC

Hello, thank you for information. Unfortunately, I checked with leftest update, and still same exception appears in Xamarin.Android 10.3 (Mono 6.10), 10.2 is fine.

Best regards,
Radoslaw Kubas

SJ Suyamburaja Jayakumar Syncfusion Team July 24, 2020 04:23 PM UTC

Hi Radoslaw Kubas,   
   
Thanks for your update.   
      
Under your account, we have created a support incident to track the status of this reported query.      
      
Please log on to our support website to check for further updates.      
      
   
Regards,   
Suyamburaja J. 


FM Fernando Mendes replied to Ramya Soundar Rajan September 25, 2020 10:42 AM UTC

Hi Radoslaw Kubas/ Fernando Mendes, 
 
We are glad to announce that our weekly NuGet was rolled out and fix for the reported issue was included in the weekly NuGet. 
 
NuGet Version: 18.2.0.46
 
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Regards, 
Ramya S 


Hi, I made the test with 18.2.0.59 version and the bug remains, please, please, fix it.


SM Saravanan Madheswaran Syncfusion Team September 28, 2020 12:36 PM UTC

Hi Fernando 
 
We would like to let you know that the reported issue occurred with specific device configuration hence only previously provided stack trace-based issue fix is not resolved yet. We can find the proper root cause and currently working on fixing the reported problem with ensuring in all possible testing devices and probably it will be included in our upcoming  weekly NuGet release which is expected to be rolled out on Oct 6,2020. 
 
Regards, 
Saravanan 


SM Saravanan Madheswaran Syncfusion Team October 6, 2020 01:15 PM UTC

Hi Fernando,  
 
The fix for reported “Not a legal OleAut date argument exception at Android” was moved for weekly update which is postponed to tomorrow [7th October 2020]. We will let you know once it gets rolled out 
 
Regards, 
Saravanan. 


SM Saravanan Madheswaran Syncfusion Team October 7, 2020 08:26 AM UTC

Hi Fernando,   
 
We are glad to announce that our weekly Nuget was rolled out today and fix for the reported “Not a legal OleAut date argument exception at Android” issue fix was included in the weekly Nuget.   
  
Nuget Version: 18.3.0.38 
  
We thank you for your support and appreciate your patience in waiting for this release. Please get in touch with us if you would require any further assistance. 
 
Regards, 
Saravanan. 
 


Marked as answer
RK Radoslaw Kubas October 7, 2020 01:29 PM UTC

Hello,

Thank you for this fix, I can confirm that it solved the problem.

Best regards,
Radek

SM Saravanan Madheswaran Syncfusion Team October 7, 2020 04:03 PM UTC

Hi Radek, 
 
Thanks for your confirmation. please don't hesitate to contact us, if you need any further assistance. 
 
Regards, 
Saravanan. 


FM Fernando Mendes October 18, 2020 12:08 PM UTC

Hi, I made the test with 18.3.0.35 version and the bug stiiiiiillll remains, please, please, fix it.

An importante note, the issue happens only in armeabi-v7a users, it not happens with arm64-v8a users!!





Xamarin Exception Stack: System.ArgumentException: Not a legal OleAut date. at System.DateTime.DoubleDateToTicks (System.Double value) <0xccb6cf78 + 0x0012c> in <5e48961868264047bfbc94f37511101f>:0 at System.DateTime.FromOADate (System.Double d) <0xccb6d62c + 0x0004b> in <5e48961868264047bfbc94f37511101f>:0 at Com.Syncfusion.Charts.DateTimeAxis.GenerateVisibleLabels () <0xc71a0eb0 + 0x001b7> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartAxis.UpdateLabels () <0xc719ada4 + 0x00113> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartAxis.ComputeDesiredSize (System.Drawing.SizeF size) <0xc719abac + 0x00113> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureHorizontalAxis (System.Collections.Generic.List`1[T] axes, System.Drawing.SizeF size) <0xc71b2a8c + 0x000f3> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureAxis (System.Drawing.SizeF size) <0xc71b25f4 + 0x002a3> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.Measure (System.Drawing.SizeF availableSize) <0xc71b084c + 0x0058f> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartBase.MeasureAxis () <0xc7182958 + 0x0013f> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartBase.UpdateArea () [0x00193] in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.ChartBase.OnMeasureChart () <0xc718246c + 0x00093> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Com.Syncfusion.Charts.SfChart.OnMeasure (System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xc7187734 + 0x001eb> in <0352ff0e930540bcbae6ebcbab874e9a>:0 at Android.Views.View.n_OnMeasure_II (System.IntPtr jnienv, System.IntPtr native__this, System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xcc4d232c + 0x0007f> in <68d553184cc64a63a1ef512c58514add>:0 at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.43(intptr,intptr,int,int)



Microsoft Visual Studio Enterprise 2019
Version 16.7.3
VisualStudio.16.Release/16.7.3+30503.244
Microsoft .NET Framework
Version 4.8.04084

Installed Version: Enterprise

Xamarin   16.7.000.440 (d16-7@358f3c6)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   16.7.0.495 (remotes/origin/d16-7@79c0c522c)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates   16.7.85 (1bcbbdf)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK   11.0.2.0 (d16-7/025fde9)
Xamarin.Android Reference Assemblies and MSBuild support.
    Mono: 83105ba
    Java.Interop: xamarin/java.interop/d16-7@1f3388a
    ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000
    SQLite: xamarin/sqlite/3.32.1@1a3276b
    Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-7@017078f

Xamarin.iOS and Xamarin.Mac SDK   13.20.2.2 (817b6f72a)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.


YP Yuvaraj Palanisamy Syncfusion Team October 19, 2020 12:31 PM UTC

 
We have fixed the reported issue and it was included in 18.3.0.38 and later. So could you please upgrade the Syncfusion nuget package version to 18.3.0.38 and later. 
 
Regards, 
Yuvaraj 


FM Fernando Mendes replied to Yuvaraj Palanisamy October 22, 2020 12:42 PM UTC

 
We have fixed the reported issue and it was included in 18.3.0.38 and later. So could you please upgrade the Syncfusion nuget package version to 18.3.0.38 and later. 
 
Regards, 
Yuvaraj 


Thanks, I will try and after post the results here.

SS Sridevi Sivakumar Syncfusion Team October 23, 2020 07:56 AM UTC

Hi Fernando Mendes,

Thanks for your update.

We will wait until hear from you.

Regards,
Sridevi S. 


FM Fernando Mendes November 11, 2020 05:40 PM UTC

Hi, I made the test with 18.3.0.42 version and the bug still remains... :((( 

In this mean time, my app lost 20% of active users and the rating was from 4.8 to 4.5. :(((

Please, I need a fix for it, or at least a workaround. I can't downgrade to the last working version because other dependencies. While I don't get a solution I will continue to lost users and rating.

;((


Version Code: 200096 Version Name: beta-1.8.6 Android: 8.0.0 Android Build: R16NW Manufacturer: samsung Model: SM-G570M CrashReporter Key: d6bebf50-6300-49d3-b61b-d0d49e2a6f73 Start Date: 2020-11-10T19:53:55.777Z Date: 2020-11-10T19:54:00.646Z Xamarin Exception Stack: System.ArgumentException: Not a legal OleAut date. at System.DateTime.DoubleDateToTicks (System.Double value) <0xc326cf78 + 0x0012c> in <1bf58901a8c94bba98a8994dc0aae009>:0 at System.DateTime.FromOADate (System.Double d) <0xc326d62c + 0x0004b> in <1bf58901a8c94bba98a8994dc0aae009>:0 at Com.Syncfusion.Charts.DateTimeAxis.GenerateVisibleLabels () <0xbd81beb0 + 0x001f7> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartAxis.UpdateLabels () <0xbd815da4 + 0x00113> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartAxis.ComputeDesiredSize (System.Drawing.SizeF size) <0xbd815bac + 0x00113> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureHorizontalAxis (System.Collections.Generic.List`1[T] axes, System.Drawing.SizeF size) <0xbd82dadc + 0x000f3> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.MeasureAxis (System.Drawing.SizeF size) <0xbd82d644 + 0x002a3> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartCartesianAxisLayout.Measure (System.Drawing.SizeF availableSize) <0xbd82b894 + 0x0058f> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartBase.MeasureAxis () <0xbd7fd958 + 0x0013f> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartBase.UpdateArea () [0x00193] in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.ChartBase.OnMeasureChart () <0xbd7fd46c + 0x00093> in <2873d2e13d6c4769b96aff89178371e9>:0 at Com.Syncfusion.Charts.SfChart.OnMeasure (System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xbd802734 + 0x001eb> in <2873d2e13d6c4769b96aff89178371e9>:0 at Android.Views.View.n_OnMeasure_II (System.IntPtr jnienv, System.IntPtr native__this, System.Int32 widthMeasureSpec, System.Int32 heightMeasureSpec) <0xc2bd232c + 0x0007f> in <47c563a564c64c0f990f3fb08cc91155>:0 at (wrapper dynamic-method) Android.Runtime.DynamicMethodNameCounter.39(intptr,intptr,int,int)


SJ Suyamburaja Jayakumar Syncfusion Team November 12, 2020 04:13 PM UTC

Hi Fernando Mendes,   
         
Under your account, we have created a support incident to track the status of this reported query.      
       
Please log on to our support website to check for further updates.      
       
    
Regards, 
Suyamburaja J. 


Loader.
Up arrow icon