#scooperpoops12-terminal

1 messages · Page 1 of 1 (latest)

crystal wind
#

hi! as far as I know you should never pair it that way.

#

you'd just ignore those prompts

#

the way you connect to the reader is via the code you write for your app

low valley
#

hey karllekko, thanks for the response! Let me try that now

low valley
#

If I ignotre the popup notification for "Pairing Request", it spins for about a minute, then pops me back to the main page on the sample app saying "No reader connected"

#

I can see this in logcat "Bluetooth unexpectedly disconnected during operation."

#

Same behavior on both devices, with fresh installs of the app

crystal wind
#

try going to your Android settings and if the reader is paired there, completely delete/forget it and then try again

low valley
#

Will do, trying that now. thanks!

#

Nope, it's not paired there

#

It's just shown as an 'Available Device"

crystal wind
#

also probably worth rebooting the reader too

low valley
#

Hah, I should know by now to always start with that.... giving it a go

#

first gotta find a paper clip!

crystal wind
#

I wouldn't press the reset button

low valley
#

oooh alright, thanks

#

I am seeing the same behavior. Is it possible an issue with the "location" would manifest itself in this way?

crystal wind
#

not sure, but I don't think it would be directly related to getting an Bluetooth error like that

#

not sure what else I can suggest beyond trying to do everything entirely fresh(freshly restarted reader, freshly reinstalled app, nothing paired in the phone's settings)

low valley
#

alrighty, thanks, karllekko. What is the expected behavior here after pressing connect? Ignore the popups asking to connect, and then it connects automatically via code?

crystal wind
#

yes

low valley
#

@crystal wind I am able to connect to a BBPOS Chipper 2X BT reader just fine through the sample app (it does not prompt me to connect via notification like the M2 was).

I talked with stripe support and sent them the serial number of the M2 reader and they will get back to me. If the BBPOS Chipper is working fine, I feel like it's a reasonable assumption this M2 reader is not behaving properly

crystal wind
#

it is possible! I don't have a M2 myself to hand yet, but whenever I had similar problems with the Chipper or Wisepad 3 it's mostly just a matter of getting things back to a clean state. On rare occasions readers can be shipped with bad firmware so it's not out of the realms of possibility