#justinadkins-terminal-android
1 messages ยท Page 1 of 1 (latest)
๐
Which device do you have?
The majority of our readers are BBPOS Chipper 2X but we will be transitioning to M2's shortly
Hi ๐
Hey!
You are referring to this integration path, correct? https://stripe.com/docs/terminal/payments/connect-reader?reader-type=usb
Yeah partially, we use something similar to connect a reader via USB. It is then still discoverable by other devices using our app when discovering via Bluetooth.
we use something similar
I'm kind of confused by that. For Chippers and M2s we have the Bluetooth and USB integration paths using Stripe SDKs. How are you integrating your Chippers currently?
We use the integration you linked for USB connections, but in our app we allow the user to toggle between USB and Bluetooth.
Okay so your integration uses both Bluetooth and USB integration paths, cool.
That makes sense
Yeah, the problem we are running into is one of our apps will be connected to a reader via USB and another one will accidentally connect to that same reader via Bluetooth. This leads to a loop of connect / disconnect.
So I want to be clear that, with the USB integration, this is a beta feature and we don't have a lot of information on it currently. However, I am reaching out to some colleagues who may know more.
Thank you! I appreciate the help. I'm aware that USB is still a beta feature.
This leads to a loop of connect / disconnect.
Right, because you've followed the recommendations and implemented a callback for the UnexpectedReaderDisconnect event
Which then fires on each POS to steal back the reader
Exactly
Unfortunately this is the current state of the USB integration. I just got confirmation internally. We have taken note of your feedback and will be tracking this issue.
Thank you @narrow dawn, I appreciate you looking into it.