Action Request(2049, true) is not supported in state ConnectingToRx

[alexdpayne]

I'm seeing similar issue to #54

Around 42 times in the last 14 days out of thousands of successful transactions.

Since upgrading from 1.14.16 to 1.32.0
Android 8.1.0
Elo-i3-22Std

Various errors:

#com.izettle.payments.android.readers.vendors.datecs.ReaderV2Transport$RxConnection getRxConnection()
Action Request(2049, true) is not supported in state ConnectingToRx
Action Ready is not supported in state ConnectedToPw

#com.izettle.payments.android.readers.vendors.datecs.DatecsReaderV2
Command 0x7C0102000001007E is not expected in state Configured
Command 0x000482180006CA040000001244 is not expected in state TransactionConfirmedByReader
Command 0x0B01020000010009 is not expected in state TransactionInitializing
Command 0x000482180006CA04000000095F is not expected in state ConfigurationStarting

Due to the requirement to upgrade to this later version for the newer bluetooth modules, I can't go back to the working version.
Any help would be appreciated.

[alexdpayne]

Although it seems a lot worse in the latest version, I have found the odd error in the old version looking back through Sentry.
Only 6.
com.izettle.payments:android-sdk-ui:1.14.16

Command 0x000482180009CF0100CA040000001285 is not expected in state PinEntranceCanceledByApp
Command 0x000482180006CA04000000095F is not expected in state Unknown
Command 0x000482180006CA04000000095F is not expected in state ConfigurationStarting
Action StartTransaction[de7056e7-2b98-465f-af71-e298283b9d70] is not supported in state TransactionStarted

[alexdpayne]

Looking at a crash log for this morning, it appears to be happening outside of a transaction.

There was a successful payment and then 45 seconds later it just crashed (no one was using the device).
So it seems to be happening in the background.

[bobzettle]

Hi @alexdpayne,

Sincere apologies for the delay in getting back to you!
This is something we are actively working on trying to solve. I'll pass your comments on to the team working on it.

[CheZhongSdk]

Hi @alexdpayne

Sincere apologies for the late update. This issue should be fixed in SDK v1.36.8 and later versions. Please try it out, and let us know if you still have the issue.

Thank you.