ArrayIndexOutOfBoundsException wrapping CroneCommand in release-1.8.9

[planetcoops]

Expected Behavior

Current Behavior

Witnessing several crashes with the following stack from the Developer Console:

java.lang.ArrayIndexOutOfBoundsException:
at com.izettle.payments.android.readers.vendors.datecs.crone.a. (a.java:64)
at com.izettle.payments.android.readers.vendors.datecs.crone.CroneCommand$Companion.wrap (CroneCommand.java:38)
at com.izettle.payments.android.readers.vendors.datecs.crone.DecryptedResponseContainerImpl.toCommand (DecryptedResponseContainerImpl.java:254)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.reduce (ReaderV2TransportImpl.java:400)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.reduce$readers_release (ReaderV2TransportImpl.java:260)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$c.a (ReaderV2TransportImpl.java:239)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$c.invoke (ReaderV2TransportImpl.java:212)
at com.izettle.android.commons.state.StateImpl.update (StateImpl.java:87)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.action (ReaderV2TransportImpl.java:238)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.doReadData (ReaderV2TransportImpl.java:768)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.access$doReadData (ReaderV2TransportImpl.java:212)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$k.a (ReaderV2TransportImpl.java:610)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$k.invoke (ReaderV2TransportImpl.java:212)
at com.izettle.android.commons.thread.c.run (c.java:2)
at java.lang.Thread.run (Thread.java:764)

and

com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$a:
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.reduce (ReaderV2TransportImpl.java:369)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.reduce$readers_release (ReaderV2TransportImpl.java:259)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$c.a (ReaderV2TransportImpl.java:239)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$c.invoke (ReaderV2TransportImpl.java:212)
at com.izettle.android.commons.state.StateImpl.update (StateImpl.java:87)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.action (ReaderV2TransportImpl.java:238)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl.access$action (ReaderV2TransportImpl.java:212)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$m.a (ReaderV2TransportImpl.java:246)
at com.izettle.payments.android.readers.vendors.datecs.ReaderV2TransportImpl$m.invoke (ReaderV2TransportImpl.java:212)
at com.izettle.android.commons.thread.a.run (a.java:2)
at android.os.Handler.handleCallback (Handler.java:873)
at android.os.Handler.dispatchMessage (Handler.java:99)
at android.os.Looper.loop (Looper.java:214)
at android.os.HandlerThread.run (HandlerThread.java:65)

Steps to Reproduce

We can't reproduce, the crashes come from Google Play Console reports.

Context

User is running:

Samsung Galaxy S8
Android 9 (SDK 28)

Failure Logs

[fabriciovergara]

Thanks for the contact.

To better investigate, do you have the email used to login in izettle sdk? if positive, try to reach us by email sdk@zettle.com since it's a sensitive information.

[planetcoops]

Sorry it's anonymous data from the Google Play Console so we only have the reported stacks.

[bobzettle]

Hi, apologies for not hearing from us. Have you managed to sort this out?
The issue will now be closed, but feel free to add a comment if you still need help and we'll get back to you shortly.