anna_error | Stripe Developers | Page 1

wide ledgeBOT Oct 6, 2025, 1:59 PM

#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1424757863770886226

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

celest flame Oct 6, 2025, 2:01 PM

#

Hi, let me grab a teammate who can help with Terminal questions. Hang tight

willow shale Oct 6, 2025, 2:05 PM

#

hey there! Can you share more about the frequency this happens, or if you've noticed any patterns yet?

#

Do you have a variaty of locations with different or consistent behaviour, or does it happen at a single location?

#

Also there's a bit of dissonance between "Error discoverReaders" and "Contactless transaction failed"

#

The first part sounds like an error during discovery, while the latter sounds like an error during payment.

#

Can you explain more about when/how this appears?

rich valve Oct 6, 2025, 2:12 PM

#

Hi,
The error appears on one of our customer’s phones right after they initiate the connection process.
The “discover” and “connection” steps are triggered sequentially by a single button, while the payment is triggered by a separate button.
I haven’t noticed any specific patterns so far — it seems to happen randomly.
Today, I ran multiple tests using the same device, and the error didn’t occur again.
The Tap to Pay account is associated with a single location.

willow shale Oct 6, 2025, 2:13 PM

#

So this is occuring on a single point of sale device?

rich valve Oct 6, 2025, 2:13 PM

#

yes

willow shale Oct 6, 2025, 2:13 PM

#

Which SDK & version are you using?

rich valve Oct 6, 2025, 2:13 PM

#

0.0.1-beta.26

willow shale Oct 6, 2025, 2:14 PM

#

I would also suggest you add some debug logging to separate the discover & connect steps to isolate the issue, as failing to discover and failing to connect can be quite different

#

For which SDK?

#

Is that react native?

rich valve Oct 6, 2025, 2:14 PM

#

i'm using React Native with Expo SDK 52

willow shale Oct 6, 2025, 2:18 PM

#

What kind of device is this happening on? (Manufacturer/model)

#

It's possibly related to aggressive battery optimizations killing the tap to pay process

rich valve Oct 6, 2025, 2:20 PM

#

Xiaomi Redmi 12

wide ledgeBOT Oct 6, 2025, 2:21 PM

#

rich valve Oct 6, 2025, 2:24 PM

#

I’m also disabling the battery saver features and the “pause app activity if unused” setting for our app, as these might affect the connection stability. This could potentially help reduce the occurrence of the issue?

willow shale Oct 6, 2025, 2:28 PM

#

As in you already did tried this, or you are trying now?

rich valve Oct 6, 2025, 2:28 PM

#

i'm tryng now

willow shale Oct 6, 2025, 2:28 PM

#

Gotcha

#

There's some general guidance for the options around this on this site: https://dontkillmyapp.com/xiaomi

rich valve Oct 6, 2025, 2:52 PM

#

Even after disabling those settings, the error has reappeared. I didn’t do anything different in terms of usage compared to before.

supple gyro Oct 6, 2025, 3:05 PM

#

Looking into if there is other guidance on this, but unfortunately Stripe doesn't have a special way of enabling this if the manufacturer disables it

#

While I'm looking, have you had a chance to add debug logging and see which specific step is failing here and with what error message?

#anna_error