- edited description
com.movesense.mds.MdsException: java.lang.IndexOutOfBoundsException: toIndex = 70
Issue #108
open
Sentry.io caught this in our Flutter app.
Mobile device model and OS version
Samsung Galaxy S8+ SM-G955F (R16NW)
8.0.0(R16NW.G955FXXS4CSB1)
Movesense mobile library version
1.63
Movesense firmware version
(will update later)
Movesense hardware version (e.g. 14451G)
(will update later)
Preconditions
Seems like sensor was just connected
Reproduction steps
Unknown
Reproduction rate
1 time so far
Logs & code usage
PlatformException(2, Error on connecting to movesense sensor: , com.movesense.mds.MdsException: java.lang.IndexOutOfBoundsException: toIndex = 70
at com.movesense.mds.Mds$1.onConnectError(Mds.java:3)
at com.movesense.mds.internal.connectivity.BleManager$6.run(BleManager.java:2)
at android.os.Handler.handleCallback(Handler.java:789)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6938)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Caused by: java.lang.IndexOutOfBoundsException: toIndex = 70
at java.util.ArrayList.subListRangeCheck(ArrayList.java:1016)
at java.util.ArrayList.subList(ArrayList.java:1008)
at com.movesense.mds.internal.connectivity.ConnectedDevice.removeData(ConnectedDevice.java:2)
at com.movesense.mds.internal.connectivity.ConnectedDevice.getNextPacket(ConnectedDevice.java:7)
at com.movesense.mds.internal.connectivity.BleManager.dataAvailable(BleManager.java:4)
at com.movesense.mds.internal.connectivity.BleManager.E(BleManager.java:1)
at com.movesense.mds.internal.connectivity.BleManager.G(Unknown Source:0)
at com.movesense.mds.internal.connectivity.c.accept(Unknown Source:6)
at j.e.b0.h.a.e(LambdaSubscriber.java:2)
at j.e.b0.e.b.j$c.h(FlowableObserveOn.java:8)
at j.e.b0.e.b.j$a.run(FlowableObserveOn.java:5)
at j.e.b0.g.l.run(ScheduledRunnable.java:2)
at j.e.b0.g.l.call(ScheduledRunnable.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
, null)
Comments (4)
-
reporter -
Are you still seeing this with the latest MDS? Our compatibility testing has passed on that phone model, so I’m intrerested to know if there is still issues.
-
- changed status to open
-
reporter I’m currently not actively working with this application, will upgrade to latest MDS if I get the chance.
- Log in to comment