#Stephen Orr
1 messages · Page 1 of 1 (latest)
You're facing the exact same issue as what's described in that Github issue? Or just a similar one? Did resetting the reader help (as it did in that Github issue)?
helped momentarily however the problem keeps returning, the customer seems to need to pair the reader at the beginning of each day which is unusual when compared to our iOS integration
similar issue, we can see the reader failing with an error message of "Bluetooth unexpectedly disconnected during operation."
Hm interesting. Can you share your device type, device serial, and what version of the stripe-terminal-android sdk you're using?
device type: WisePad 3
device serial: WPC323105001416
Unsure of the stripe terminal android SDK version though, apologies! I didn't develop the solution myself. Here to pass on any info I can get on the matter just unfortunately!
Ah ok. Are you a developer?
Unfortunately not, but would have access to the Stripe dashboard if that could help me any
Gotcha. It'd be ideal if we could speak to your developer (would like to see code as well), but let me see if I can get a colleague with more android/terminal experience to take a look with what info we do have
I think disconnects and reconnecting in response to that might be expected
When you say pair, you mean connect in your app, right?
IIRC, there should be no device-level pairing used with our readers
yes, connecting within the application itself
I see logs for that reader SN that suggest its generally working. Which seems to align with what you say.
Aside from the morning re-connect, this is also working in android to collect payments?
The logs i see are primarily ios