Keep getting "Bluetooth unexpectedly disconnected during operation." error

[dwiyasko]

deps: com.stripe:stripeterminal:2.21.1

Reader: Wisepad 3

Sometimes, in some Sunmi V2s devices, we face reader connection failure with the error message: "Bluetooth unexpectedly disconnected during operation."

You can see the all process we did during the connection to Wisepad 3 reader in the attached picture.

The questions:

1. What Stripe team suggest when the app is killed? Currently, we disconnect the reader programmatically, so when the user re-opens the app, it will start the connection process again.
2. What's your recommendation for user behavior? Is it okay if the user closes the app frequently or do you suggest the user keep the app open? Let's say after every payment is done, the cashier will close the app,

Because we found that when the app got killed after being idle for a long enough time, the reader status is still connected, but our app lost the connection actually, so the app cannot connect to the reader because the reader status is still connected.

So, that's why we come up with the first solution.

Also worth to notes, we don't use an auto reconnection feature, we provide a CTA to the user when the reader got disconnected and do manual reconnection instead.

the event token: looking_for_BT_reader -> Start the discovery connecting_bt_reader -> Last saved reader found, start the connection stripe_terminal_connecting -> Getting Stripe Connection Token

[billfinn-stripe]

Hi @dwiyasko -- I realize that we haven't responded to this issue for quite some time (sorry!), but can you upgrade to the latest version and check if it's still an issue? We had a number of Bluetooth-related changes between 2.x and 3.x, so it would be helpful if we could get clear reproducible steps on the latest version of the SDK (3.5.0).

[xiaoshen-stripe]

Closing due to inactivity. Please feel free to reopen if this is still an issue. Thanks