#juanse-terminal-android-pairing
1 messages · Page 1 of 1 (latest)
juanse-terminal-android-pairing
@strange crypt can you provide more specific details?
Sure, we develop a packafe for sdk version 2 for react native => https://www.npmjs.com/package/react-native-stripe-terminal-2.0-sdk, and works well with BBPOS black but when we will use Stripe terminal M2 and wisepad 3 that just in android in IOS working well for any reason i had an error with the bluetooth and first i need to connect direct the reader with the phone device by setting device and also i can connect the reader if not i just can discover the reader but when i try to connect that reader i obtain an error the bluetooth connection for a pin or something like that.
when we will use Stripe terminal M2 and wisepad 3 that just in android in IOS working well for any reason i had an error with the bluetooth
can you rewrite that sentence? I don't follow the train of thoughts there
first i need to connect direct the reader with the phone device by setting device
same here I don't understand what that could mean. You should never pair with the reader in the phone setting
so my question is if with some Android version maybe 12+ i need to do an extra config for pair the reader in the client side or is mandatory first pair the reader with the device and then i can do that automatic with my app
or is mandatory first pair the reader with the device
what does that mean exactly
you should never go in the Bluetooth setting on your phone/tablet to pair with the reader
exactly that is my problem with those two readers, i need to go to setting for pair the readers and then in my app i can to connect that reader, if i cannot do that, i can see the readers discovered but when i try to connect a reader, i obtain an bluetooth error (couldn't pair with "serial number" incorrect pin)
yeah you can't do that
you really should never connect in BT, that will prevent you from connecting later
ok so is normal that behavior in android devices, maybe is a permission or extra config in Android side, because in IOS it doesn't has
maybe any suggestion that you have for that case, because i follow the documentation and doesn't has an instruction for my issue.
Unfortunately, you aren't really explaining what the problem is despite the back and forth, I'm sorry