[Tap To Pay] Reader has been disconnected unexpectedly on Android devices

[ThanJack]

Describe the bug
After putting the Android app in the background for some time, then reopening the app to do the first Tap to Pay transaction causes the following issue happens:

[Stripe terminal]: didReportUnexpectedReaderDisconnect { message: 'Reader has been disconnected unexpectedly',
  code: 'UNEXPECTED_ERROR.UNEXPECTED_SDK_ERROR' }

It happened after after creating the Payment Intent by the createPaymentIntent function and before the collectingPaymentMethod function executes. Then the collectingPaymentMethod function throws this error, which causes the transaction to fail:

{ code: 'INTEGRATION_ERROR.NOT_CONNECTED_TO_READER',
  message: 'LocalMobile reader is not connected' }

To Reproduce
Steps to reproduce the behavior:

1. Put app to the background for a while (eg. more than 2 hours).
2. Reopen the app, start the first transaction.
3. Tap To Pay screen appears, try to tap a card.
4. The issue above happens.

Expected behavior

The Reader should not be disconnected unexpectedly when doing the transaction.

Stripe Terminal React Native SDK version

• ^0.0.1-beta.17
• ^0.0.1-beta.18

Smartphone (please complete the following information):

• Device: Google Pixel 3a
• OS: Android 12

[tzecheng]

Hi,
It also happens on a Pixel 4, running Android 13.
Note that the error is random. We left the app in the background over multiple periods, sometimes the payment works on re-opening the app, sometimes the above error happens.

[nazli-stripe]

@tzecheng and @ThanJack can you share account and serial numbers so we can investigate?

[tzecheng]

Hi @nazli-stripe , I can't find the account and serial numbers when the payment is cancelled.

The latest has id: pi_3PF7CwEcr8OExvfT1zxs98vO

Attached bugfender screen shot
android cancelled 4.pdf

Hope that helps. Thanks.

[KillianLarcher]

It also happens on a Pixel 4, running Android 13.
Note that the error is random. We left the app in the background over multiple periods, sometimes the payment works on re-opening the app, sometimes the above error happens.

Same problem here on Samsung Tab Active 3, running Android 13.

[nazli-stripe]

This appears to be a potential issue with our native Android SDK, we are investigating internally. Will update this ticket with new information

[tzecheng]

Hi @nazli-stripe ,

This is one of the latest instances where there is a serial number it it helps:
serialNumber: '7808ed1a-4ea0-4f73-9c83-5a7bc28a04f4'

[tzecheng]

Here's another serial number:
serialNumber: 'b7c812c4-0237-4b3b-9366-cc9318004df0'

[KillianLarcher]

Any news? @nazli-stripe

[tzecheng]

Hello, @nazli-stripe ,
Any progress on this?

[tzecheng]

Hi there,
Here's is a screenshot of latest failure,
Serial number: 6b16a116-d082-4568-af55-34e1104bdf3a

[tzecheng]

Hi there,

Have tried with
^0.0.1-beta.19 and ^0.0.1-beta.20

Problem is still there.
Latest serialNumber: '2e941d93-52cb-4eea-a3db-9fbe1ecd1c13'

[nabilfreeman]

We are also experiencing this. The only solution so far has been to disconnect and reconnect the reader every time we want to initiate Tap to Pay. It looks like the library is unable to monitor the connection state of the reader in background and auto reconnect properly.

[tzecheng]

Hi there,
Have updated to v0.0.1-beta.22, but this problem still appears occasionally.
Latest serial no: