#beypazarigurusu_unexpected

1 messages · Page 1 of 1 (latest)

cyan meteorBOT
#

👋 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/1302925527501377536

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

glossy pasture
#

hi there!

#

can you share the code that is trowing that error?

stark perch
#

Hi! We tried both the react native library and the android SDK itself directly. The step we get the error is calling discoverReaders after the SDK initialization. We're sure that the initialization step is working correctly. The same sample code works on a compatible mobile phone -- we can discover the device as a reader using localMobile method. But on S700 devkit, we are getting the respective errors I reported.

#

So the code would be basically two snippets to call discoverReaders with "handoff" and the "localMobile" methods.

glossy pasture
#

got it! I recommend contacting Stripe support directly, they will have more time to investigate this issue. make sure to include all relevant information (full error message, actual code samples, etc.). https://support.stripe.com/contact

stark perch
#

Thanks. FYI, we already have a support contact we pinged on this. I just wanted to make sure running the SDK on S700 for this use case is something that's not flat out unsupported.

#

One thing we found after a quick search was this comment:

https://github.com/stripe/stripe-terminal-react-native/issues/788#issuecomment-2356409643

How do we go about enabling this for our account as well? We do have access to the tap to pay beta feature and an S700 devkit.

GitHub

Describe the bug The following versions cause discoverReaders to never return a reader to connect to: implementation("com.stripe:stripeterminal-core:3.8.0") implementation("com.strip...

#

Because we're suspecting not having this access might be the blocker.

glossy pasture
#

that's possible yes! but again the solution here would be to contact Stripe support. we can't enable any flags on Discord.