SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and iOS Chart & Android Chart Components

0
0

I have many users who have been sending crash reports with this stack trace and I can’t figure out what part of our code would be triggering this since the stack trace doesn’t mention any classes that are we’ve coded. Any idea what could be triggering this based on the stack trace?

java.lang.ArrayIndexOutOfBoundsException: index
at com.scichart.core.model.IntegerValues.get(IntegerValues.java:164)
at com.scichart.charting.visuals.layout.CanvasLayout.getChildDrawingOrder(CanvasLayout.java:75)
at android.view.View.populateAccessibilityNodeInfoDrawingOrderInParent(View.java:7053)
at android.view.View.onInitializeAccessibilityNodeInfoInternal(View.java:7006)
at android.view.ViewGroup.onInitializeAccessibilityNodeInfoInternal(ViewGroup.java:3232)
at android.view.View.onInitializeAccessibilityNodeInfo(View.java:6622)
at android.view.View.createAccessibilityNodeInfoInternal(View.java:6581)
at android.view.View.createAccessibilityNodeInfo(View.java:6566)
at android.view.accessibility.AccessibilityRecord.setSource(AccessibilityRecord.java:145)
at android.view.accessibility.AccessibilityRecord.setSource(AccessibilityRecord.java:119)
at android.view.View.onInitializeAccessibilityEventInternal(View.java:6518)
at android.view.View.onInitializeAccessibilityEvent(View.java:6506)
at android.view.View.sendAccessibilityEventUncheckedInternal(View.java:6371)
at android.view.View.sendAccessibilityEventUnchecked(View.java:6356)
at android.view.View$SendViewStateChangedAccessibilityEvent.run(View.java:23903)
at android.view.View$SendViewStateChangedAccessibilityEvent.runOrPost(View.java:23936)
at android.view.View.notifyViewAccessibilityStateChangedIfNeeded(View.java:9488)
at android.view.View.setFlags(View.java:11685)
at android.view.View.setVisibility(View.java:8082)
at com.scichart.charting.visuals.annotations.AnnotationBase$17.run(AnnotationBase.java:268)
at android.os.Handler.handleCallback(Handler.java:836)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:208)
at android.app.ActivityThread.main(ActivityThread.java:6267)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1063)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:924)

Version
2.0.0.1654
  • Yura Khariton
    Hi Ricardo. It’s hard to tell what could cause this exception without seeing the code. Can you provide a project which reproduces this issue so I could debug it on my PC?
  • Ricardo De Amorim
    Unfortunately, we have not been able to find steps to reproduce this on our end, and because the stacktrace doesn’t reference our code at all, we don’t really know what part of the code could be causing this. I could potentially provide copies of the code that draws graphs in our app to you in private if you send me a contact address, and maybe you could review it and see if we are misusing the scichart API in some way?
  • You must to post comments
0
0

Hi Ricardo,

As I see from stack trace this exception occurs in CanvasLayout which we use as base class for several parts of SciChartSurface ( e.g. one to place annotations, another for modifiers etc). Unfortunately exception doesn’t show in which part of the chart it occurs so without project it would be hard cause of the problem.

However I noticed that you wrote that you use v2.0.0.1654 which was released in 2017. Please try to update to the latest release from our website (v2.2.1.2391). We fixed many bugs ( including rewriting parts of CanvasLayout where your exception occurs ) since that time.

Best regards,
Yura.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.