#furd_unexpected

1 messages · Page 1 of 1 (latest)

glass torrentBOT
#

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

📝 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.

shut elm
#

You can check my past messages, but I've tried every step. I've even factory resetted my M2 terminal just now and it didn't work.

#

I am using react native deployed to android

hollow elbow
#

Hi 👋

Quick question. Did you ever pair the M2 using the Android OS bluetooth pairing?

#

I'm pulling up the reader logs now

shut elm
#

yeah i did at one point to confirm my android's bluetooth settings but ive made sure to disconnect and forget the bluetooth pairing

hollow elbow
#

Okay I am seeing a lot of unexpected and unhandled disconnections in the logs

#

So far nothing else

#

Except some situations where the Discover Readers action was explicitly canceled

shut elm
#

yeah i did

#

anything that explicitly says why bluetotoh disconnected?

hollow elbow
#

Have you implemented the disconenction handling logic we outline here?

#

The reader disconnection is occurring at the OS level (below the Stripe SDK). Unfortunately, this means we cannot surface much info beyond the fact that it happened

shut elm
#

Really weird. Because I"ve used this terminal to accept payments before on the Payments app

hollow elbow
#

What do you mean "the Payments app"? Is this the application you are developing in React Native?

shut elm
#

this app does connect to my m2 and it does take payments. can confirm via my stripe

hollow elbow
#

Ah, that app is made by a 3rd party (not directly by Stripe) so unfortunately I don't have direct insight into how they handle their Bluetooth connectivity.

#

You never answered my question earlier. Have you implemented the automatic reconnection logic we document here?

shut elm
#

oh yes, i have

hollow elbow
#

Okay, just wanted to make sure we didn't overlook anything obvious

#

Hmmm.... I wonder if that app is handling the disconnects on it's own. We describe that here:

To handle reader disconnects yourself, you can do the following:

  • Set autoReconnectOnUnexpectedDisconnect to false during connection.
  • Handle the disconnect callback to display a message in the app alerting the user that the reader unexpectedly disconnected and initiate reader discovery and connection.
shut elm
#

i feel like ive exhausted all my options

#

its really weird because all other core functionalites of stripe terminal sdk work

hollow elbow
#

And are you able to replicate this behavior across all mobile devices you use the M2 with?

shut elm
#

on the iphone with the 3rd party payments app, i can connect

on the android with example app, i cant connect

hollow elbow
#

Have you tried multiple android devices?

shut elm
#

i dont have another android device

#

im looking at borrowing a friends android phone

#

and im currently in contact with the android device provider who gave me the device im currently using

hollow elbow
#

What device is it?

#

And what version of Android is it running?

shut elm
#

im curently using a
22in-I-Series-4-Value from ELO
running Android 10

hollow elbow
#

Hmmmm... I thought we had docs that listed what kinds of Android devices were supported. That may not be an NFC chip we support or the Android OS version may be out of date

shut elm
#

I've seen the same exact android device connecting to a m2. and it can discover reader. and it can connect via bluetooth through the regular means. so im so confused why it cant establish the connection through the stripe sdk.

hollow elbow
#

I've seen the same exact android device connecting to a m2. and it can discover reader
Unless you are referring to a Stripe M2 and these actions were performed with the Stripe SDK, I cannot guarantee that this is transferrable.

shut elm
#

like same hardware provider, same stripe m2 terminals

hollow elbow
#

I don't have any insight into their code so I cannot offer any advice about how they are handling their readers.

#

I understand this is frustrating. And unfortunately, because these are physical readers that interact with physical hardware we don't control (the mobile devices) and we don't have insight into the environment (any interferance, etc.), the amount of guidance we can provide for these specific kinds of issues is limited.

glass torrentBOT