Terminal getting stuck with bluetooth connection

We are having issues with the terminal getting stuck with the bluetooth connection.
We think the issue might be that when calling checkout your SDK goes in forground and stops the main activity (our app) and therefore the thread will be dead and can't get notified.

Even your sample app has the same issue.

07-24 11:10:06.426 4023-12130/com.nuvopoint.tillty E/SumUp: (SourceFile:150)@BtSmart-Receiver | onTransportError() PinPlusReaderError{Name = NOT_ALLOWED mErrorCode=3}
07-24 11:10:07.267 4023-12130/com.nuvopoint.tillty E/SumUp: (SourceFile:150)@BtSmart-Receiver | onTransportError() PinPlusReaderError{Name = NOT_ALLOWED mErrorCode=3}
07-24 11:10:07.272 4023-4023/com.nuvopoint.tillty E/SumUp: (SourceFile:759)@main | Reader error received: PinPlusReaderError{Name = NOT_ALLOWED mErrorCode=3}
07-24 11:10:07.347 4023-8335/com.nuvopoint.tillty W/MessageQueue: Handler (android.os.Handler) {a8ce003} sending message to a Handler on a dead thread
    java.lang.IllegalStateException: Handler (android.os.Handler) {a8ce003} sending message to a Handler on a dead thread
        at android.os.MessageQueue.enqueueMessage(MessageQueue.java:545)
        at android.os.Handler.enqueueMessage(Handler.java:661)
        at android.os.Handler.sendMessageAtTime(Handler.java:630)
        at android.os.Handler.sendMessageDelayed(Handler.java:600)
        at android.os.Handler.sendMessage(Handler.java:537)
        at android.os.Message.sendToTarget(Message.java:418)
        at com.sumup.readerlib.pinplus.transport.BtSmartReceiver.onConnectionStateChange(SourceFile:66)
        at android.bluetooth.BluetoothGatt$1$4.run(BluetoothGatt.java:268)
        at android.bluetooth.BluetoothGatt.runOrQueueCallback(BluetoothGatt.java:789)
        at android.bluetooth.BluetoothGatt.-wrap0(Unknown Source:0)
        at android.bluetooth.BluetoothGatt$1.onClientConnectionState(BluetoothGatt.java:264)
        at android.bluetooth.IBluetoothGattCallback$Stub.onTransact(IBluetoothGattCallback.java:70)
        at android.os.Binder.execTransact(Binder.java:682)

This stackoverflow question outlines the problem, along with a potential answer:
https://stackoverflow.com/questions/8040280/how-to-handle-handler-messages-when-activity-fragment-is-paused

[vfoixcable]

Thanks for the feedback.

The warning is not the issue here. Still, we agree it is unnecessary noise and it will be fixed in the next sdk version.

Regarding the issue, we identified it internally. It will be part of the next SDK release as well.

Thank you for the update!

So the main issue regarding the terminal getting stuck will be fixed in the upcoming version of the SDK?
When can we expect this update?

[vfoixcable]

Yep!
We aim at releasing a next version of the SDK by end of Q3

And what can we do for our clients in the meantime?
Any ideas to somehow avoid the issue (workaround) will be welcome!

[vfoixcable]

The issue typically happens if the app is killed in the middle of a transaction. (e.g. while entering the pin, or landing on the signature screen).

To recover from this issue, switching off and back on the reader will be the workaround.

It's not getting killed, but the since the SDK pushes itself on top of the main activity, the activity gets stopped. This is most likely also related to the 'sending message to a Handler on a dead thread' issue.

Is there any state in your SDK that we can check to see if this has happend so that we can reset?

[vfoixcable]

The warning is there because the bt got disconnected. This is a side effect but not the source of the issue.

Unfortunately, we dont provide any callback to check on that in the current implementation.

Ok, but then tell me if you need any help from us with the update so we can speed up the process.

[FilipMatys]

Having the same issue (exception). We are working on an integration and yesterday everything worked fine.

Today, the first payment worked. The second got stuck on "Checking card reader" and the terminal Bluetooth icon kept flashing. Worked after resetting terminal, but only once.

The official SumUp application works fine.

Any help regarding a workaround would be greatly appreciated, as this is a blocker for us.

[vfoixcable]

We aim at releasing a next version of the SDK solving this issue programmatically by end of Q3.

For the moment, switching off and back on the card reader will be the workaround.

[vladaman]

Great, will wait for next version. Can you think of a use case, where SumUp will be used at self-service environments please!

• No error messages, possibility to skip Error Screen
• Should not get stuck and should always return back to the original software
• Should timeout accordingly

This would be a huge win!

[jahenry]

@vladaman appreciate your feedback however unfortunately we do not support self-service (eg. vending machine) setups today.

Hey @vfoixcable any news on the update?

[vfoixcable]

Hi @nuvoPoint , still aiming at end of Q3. So far, we are on track! It could happen end of next week or beginning of the one after.

[FilipMatys]

Latest version 3.1.0 seems to be working properly now.