Closed RogerioNT closed 2 years ago
@RogerioNT Just to confirm, it does happen when you get back to onActivityResult from a Payment or something else specific from your app?
Hi, since we haven't heard back during the last month we will be closing this issue now. Feel free to reopen with new comments if needed.
Expected Behavior
This issue is intermittent, it happen after zettle return to our application on "onActivityResult" then crash the app.
Current Behavior
What is the current behavior?
unknown
## Failure Logs
Fatal Exception: com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1$UnexpectedActionForState Action FailInstallment[fa29fcd5-8bcd-4712-b5de-7b899ab01ff0] is not supported in state Ready com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1.mutate$zettle_payments_sdk (SourceFile:2) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1.reduce (SourceFile:338) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1.reduce$zettle_payments_sdk (SourceFile:30) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1$action$1.invoke (SourceFile:2) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1$action$1.invoke (SourceFile:1) com.izettle.android.commons.state.StateImpl.update (SourceFile:7) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1.mutate$zettle_payments_sdk (SourceFile:1) com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV1.mutate$zettle_payments_sdk (SourceFile:28) com.izettle.payments.android.payment.InstallmentManagerImpl$ReaderStateObserver$onWaitingForInstallment$1.invoke (SourceFile:2) com.izettle.payments.android.payment.InstallmentManagerImpl$ReaderStateObserver$onWaitingForInstallment$1.invoke (SourceFile:1) com.izettle.android.commons.thread.EventsLoopKt$sam$java_lang_Runnable$0.run (SourceFile) android.os.Handler.handleCallback (Handler.java:836)
android.os.HandlerThread.run (HandlerThread.java:61)