dylan-hollohan_error | Stripe Developers | Page 1

marsh owlBOT Mar 19, 2026, 4:28 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/1484227079120879766

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

dylan-hollohan_code, 3 days ago, 3 messages

#

opal axle Mar 19, 2026, 4:33 PM

#

Hello 👋

Is it possible that updating TLS root certificates broke our old SDK connection?

Can you clarify what you mean here? I agree with my colleague that I would expect the existing version of the RN SDK to continue working as expected unless you upgraded or changed something about your integration.

And this fails when you attempt to discover readers for TTP?

honest dagger Mar 19, 2026, 4:37 PM

#

I can roll back some dependabot upgrades I did around that time but it was working hundreds of times per day until the beta29 was released (which we ignored for ~5 days until dependabot brought it to our attention), Once we upgraded to beta29, we noticed the hardware issue with our device's Android keystore version 41 that we have explicitly causing an issue. So we downgraded back to beta28, at which point the discoverReaders step was never succeeding anymore.

#

Honestly I dont understand my question about TLS certificates either but I can't find any good reason why the old SDK stopped working, so I'm digging through changelog to understand what it could be

#

Nobody else is complaining that beta28 suddenly broke for them?

opal axle Mar 19, 2026, 4:41 PM

#

Not that I am aware of, no. But it definitely could be related to some other updates. It sounds like the communication to the Stripe services are not succeeding. I'm looking into the underlying Android code for this service to try an understand under what conditions this error is thrown

honest dagger Mar 19, 2026, 4:44 PM

#

Okay, can you leave this thread open for at least like 3 hours while I test some things on my side? Last time the thread got closed a little quickly.

opal axle Mar 19, 2026, 4:51 PM

#

We generally close threads for inactivity after some periond of time ranging from 30 minutes to 1 hour.

#

I'm also raising this issue internally so I may have follow up questions for you about your integration and device config

honest dagger Mar 19, 2026, 4:53 PM

#

Excellent, if I find out that we broke it on our side and it was a coincidence I'll let you know. rolling stuff back on my side now

opal axle Mar 19, 2026, 4:54 PM

#

Just so I'm clear, the upgrade to beta.29 failed due to requirements for the Android keystore, correct?

#

Looking at the Changelog, I'm guessing it's this requirement:

Android Tap to Pay now requires that your Android device's KeyStore supports hardware-backed key agreements (FEATURE_HARDWARE_KEYSTORE version 100+) and Android 13 (API 33) as a minimum OS version. (from native 5.0.0)

honest dagger Mar 19, 2026, 4:56 PM

#

that's right, so the hardware provider we work with is rolling out a model with 100+ keystore and ECDH eventually, but timeline is tight for us to order those and re-write stuff.

opal axle Mar 19, 2026, 4:57 PM

#

Okay that makes sense

opal axle Mar 19, 2026, 5:12 PM

#

Unfortunately we have pressure on us to keep bumping security settings in order to allow us to make transactions on card networks. I'm digging into the code and a keystore failure would surface like this

honest dagger Mar 19, 2026, 5:14 PM

#

k thanks for looking!

opal axle Mar 19, 2026, 5:16 PM

#

It's learning for me too because generally we don't need to dig this deep into how the underlying systems work.

marsh owlBOT Mar 19, 2026, 5:17 PM

#

honest dagger Mar 19, 2026, 5:35 PM

#

(keeping thread alive)

restive rain Mar 19, 2026, 5:36 PM

#

hello! sorry, taking over for my colleague and the server is a little busy atm

#

but i will get back to you asap

honest dagger Mar 19, 2026, 5:36 PM

#

all good I just didn't want the bot to close it

restive rain Mar 19, 2026, 5:43 PM

#

i suspect we might need to go down the route of turning this into an email support case, would you be open to that if we can't get you an answer shortly?

honest dagger Mar 19, 2026, 5:43 PM

#

Yes that's fine.

honest dagger Mar 19, 2026, 6:14 PM

#

Can email dhollohan@rafflesystemsinc.com if needed\

marsh owlBOT Mar 19, 2026, 6:15 PM

#

Hello @honest dagger, we have sent you a direct message, please check it at https://discord.com/channels/@me/1484254038362034250

🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.

restive rain Mar 19, 2026, 6:16 PM

#

i just sent you a message with details explaining how you can create a case! let me know once you fill that out and i can grab it

#

i got it!

#dylan-hollohan_error

Hello @honest dagger, we have sent you a direct message, please check it at https://discord.com/channels/@me/1484254038362034250