Tap to Pay error: "No reader is connected. Connect to a reader before trying again.

[AnshulMindbody]

Some users are experiencing the error "No reader is connected. Connect to a reader before trying again." while using the Stripe iOS SDK for Tap to Pay, even though they are on the latest version of the Stripe SDK. Error occurred during discovery and connect reader.

[AnshulMindbody]

@maxa-stripe @xiaoshen-stripe

[xiaoshen-stripe]

Hey @AnshulMindbody thank you for raising, I've let our Tap to Pay team know to take a closer look.
By latest version - assuming you mean Terminal iOS SDK 3.7.0 [0].

Also, wondering if you can provide steps to reproduce this error? that would be helpful for us triage.
Thanks

[0] https://github.com/stripe/stripe-terminal-ios/releases

[sjl-stripe]

It would also be helpful if you could provide the following information so we can look at our logs:

• the device serial number
• approximate time that the issue happened

[rscherf]

I also just had a user experience this issue:

acct_1Pv2Hm04oxkN75Ou on StripeTerminal 3.8.1

9/4/24 (around 6:30pm)

This was a CA user attempting to use TTP with multiple Interac debit cards.

[mindy-stripe]

hey @rscherf @AnshulMindbody -- thanks both for your reports. We're currently gathering information and investigating this issue.

If you or your users are able to reproduce the bug, we'd like to collect more information to work with Apple to determine if there is a problem on their side. Could you please install this Tap to Pay Logging Profile and try and reproduce?

Any device UUIDs, timestamps of when the issue occurred, and PaymentIntent IDs would help us greatly with debugging further. Thanks!

[rscherf]

Hey @mindy-stripe, probably not possible to get a user to install the debugging profiles onto their devices.

Here are some sample PaymentIntent IDs however: pi_3PvSfX04oxkN75Ou0ClXDYiS, pi_3PvSfw04oxkN75Ou0wIoCtcG, pi_3PvSfX04oxkN75Ou0ClXDYiS.

[AnshulMindbody]

@mindy-stripe Any updates on the issue?

[AnshulMindbody]

@mindy-stripe Any updates on the issue?