#Donnadonna

1 messages · Page 1 of 1 (latest)

agile hullBOT
drifting copper
#

Hello! You shouldn't be pairing with your device through your android device - that's likely what's causing hte issue here

#

Don’t use mobile device settings to pair with your reader. Pairing the reader through device settings makes the reader unavailable to connect to your app.

unreal jasper
#

hey Karbi, the notification from device prompted up automatically, and I am connecting with SDK not through the device settings

#

just tried to ignore the system pair request, got this error:
LOG [Stripe terminal]: didReportUnexpectedReaderDisconnect {"code": "UNEXPECTED_ERROR.UNEXPECTED_SDK_ERROR", "message": "Reader has been disconnected unexpectedly"}

here are more information, I am using WisePad3 and device is Android

drifting copper
#

Gotcha - so you're talking about the system pairing notification, not pairing thorugh the mobile device settings

#

What version of the SDK are you using?

unreal jasper
#

I think it's in beta:
"@stripe/stripe-terminal-react-native": "^0.0.1-beta.11",

drifting copper
#

Can you try with the latest version? v0.0.1-beta.13
I believe there was a change made in 2.22.0 of our Android SDK, which is what v0.0.1-beta.13 is using

unreal jasper
#

sure I will give a shot

unreal jasper
#

just updated to version v0.0.1-beta.13, same error here,
only happen when first time pair with a terminal , call connectBluetoothReader(), no response and no error, hanging at connecting status:
LOG [Stripe terminal]: didChangeConnectionStatus connecting

drifting copper
#

It's just the first time? It works when you try it again?

agile hullBOT
unreal jasper
#

yup, just the first time, when I quit the app and reopen, everything works great

drifting copper
unreal jasper
#

but if the terminal was not connected before, want to connect as first time, will have this issue

drifting copper
#

If that newer version of the react native still has the issue I'd recommend writing into support (https://support.stripe.com/contact) so they canflag the issue to the terminal team. It may be the we fixed the issue for some android devices, but not others and a fix would need to be made