#Juanse Blankfactor

1 messages ยท Page 1 of 1 (latest)

blazing basinBOT
proper plover
#

Hi there. Can you describe what you're seeing?

tame dew
#

Currently i have an issue with the last android version stripe terminal sdk V 2.16.0, when i try to connect a M2 reader the first time and the device needs to paring the reader with the android device, that request is in hold and we cannot anything, we need to close the app and open again then we can to connect the reader with normality because we don't have that paring the reader with the device just connect to the reader and the app has a normal behaviour. I attached a video with an example.

#

the problem is the next:

Summary:
When I try to pair the first time, it only happens the first time the reader needs to pair with the android device, when the device was paired with the android devices and the reader is found in paired devices in the bluetooth option that behavior does not exist.

Case:
In the app and I try to connect a reader the first time, the reader is discovered and then I try to connect it, i obtain the next pop-up that is native for pairing the reader with my device.

#

When i tap in Pair, 'Sorry that device is in spanish ๐Ÿ™‚ but Vincular is Pair' anyway so in that case the app is bloquer, we cannot do anything the only way is kill the app and open again, but when reopen the app and again discover the reader and connect the reader the behavior is well and in that case i can to connect the reader an do payments well, because the reader was paired the last time and i don't see that pop up just the reader can do join with the device because right now is paired with the device.

I see the logs and I think that's an error with the bluetooth service, because when that happend the service show "unregister the app" and "close the service", for that reason the sdk waits for a response from the service but that response does not arrive and the app is bloquer.

proper plover
#

Ok thanks for all the details. Let me try to get a colleague who is a bit more versed in terminal to take a look at this

tame dew
#

Awesome, thanks a lot for the support

lean rampart
#

Hello ๐Ÿ‘‹
Stepping in here
Have you tried connecting the reader to a different phone to see if the behavior changes?

tame dew
#

yep is the same behavior, also i have the last firmware in the reader is the same behaviour with the WS3 as well.

lean rampart
#

Can you share the reader serial number in text here?

tame dew
#

sure

#

STRM26139009193

lean rampart
#

You said it not working with the latest SDK version. Does it work fine with an older SDK version?

tame dew
#

well that is curious because in the version 2.14.0 it bug are more heavy because we need to connect the reader directly in bluetooth setting directly because the bluetooth service sdk not showing the pair popUp, now in this version it showing that but has that little bug.

lean rampart
#

You shouldn't be connecting to the reader via the Device Settings. As that prevents the reader from showing up in the app. You should always use the SDK in order to connect to the reader.

I am not seeing any recent logs on our end with this reader. The logs are from last week (or the week before) where we see that the bluetooth was disconnected unexpectedly. It might be something with your device OR the app itself.

#

I don't know Spanish so can you share more information about the options that you see on this screen? Their rough translations are fine too.

tame dew
#

sure the first option is block, the next is cancel and the last is pair.

lean rampart
#

And the checkbox?

tame dew
#

Allow to the access to contacts and call history

lean rampart
#

Okay, Can you try following for me?

1/ Unpair OR forget the reader from Bluetooth menu in your phone's settings
2/ Uninstall the Example Terminal App
3/ Reboot your phone and the reader
4/ Install the Example App
5/ Try to connect to the reader from the App only

tame dew
#

๐Ÿซก

#

Ok i did that same behaviour, please see the logs two minutes ago

#

right now the app is in "connecting..." state

lean rampart
#

can you share a screenshot?

tame dew
#

sure

lean rampart
#

Ah I see what you mean... Hmm, I'll need some time to reproduce this issue on my end to see if this is really a bug in the SDK. Can you write into our support team (in your preferred language) with following information:

  • Your example server-side code
  • Your example client-side code (if you've made any changes)
  • SDK version
  • Android OS version
  • Reader Serial number
  • Any videos OR screenshots you can provide
tame dew
#

here is better

lean rampart
#

Don't forget to mention that you spoke with hanzo on discord

#

I'll grab the ticket and respond as soon as I find something

#