StillTrickie-terminal-sdk-ios | Stripe Developers | Page 1

fierce skiff Jan 21, 2022, 6:07 PM

#

Hello 👋

reef sleet Jan 21, 2022, 6:08 PM

#

Hi Hanzo, hope you are well

fierce skiff Jan 21, 2022, 6:09 PM

#

Yup doing well. Ready for the weekend 🙂

can you send me the terminal ID so that I can look into it?

reef sleet Jan 21, 2022, 6:10 PM

#

Weekend, what is one of those?! What Terminal ID are you after?

fierce skiff Jan 21, 2022, 6:11 PM

#

WisePad3 Card Reader

reef sleet Jan 21, 2022, 6:13 PM

#

The id provided by the sdk is nil, so the serial number good?

#

WPC323105002323

fierce skiff Jan 21, 2022, 6:15 PM

#

AH! nvm
we don't need it.
This is actually an expected behavior with Bluetooth Readers.

https://stripe.com/docs/terminal/payments/connect-reader?reader-type=bluetooth

You probably want to forget the device to stop auto pairing

reef sleet Jan 21, 2022, 6:16 PM

#

Why does your SDK not return a already connected reader?

#

This is the issue, don't mind it auto-connecting, but our app can not connect to a reader if your SDK is not returning it

#

If the device is connected via normal iPhone discovery then surely your SDK should return a connected reader? Terminal.shared.connectedReader should return a reader not nil

fierce skiff Jan 21, 2022, 6:21 PM

#

Why does your SDK not return a already connected reader?
definitely understand your frustration with this. This is certainly a limitation with the SDK right now.

From the link above:

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.

reef sleet Jan 21, 2022, 6:23 PM

#

This is an operational nightmare at the moment because we have 400+ card readers with our customers and 5-10 issues a day with this.

Are you able to solve this?

#

Do you know that even if you forget the Card Reader in mobile device settings, pair with the app, force close the app your device will connect again!

Thus requiring the need to constantly forget the reader.

#

All down to the misuse of force quitting because users think that saves battery! 😆

fierce skiff Jan 21, 2022, 6:27 PM

#

This is an operational nightmare at the moment because we have 400+ card readers with our customers and 5-10 issues a day with this.

Are you able to solve this?
My apologies.
Unfortunately, this isn't something our team handles.
We will definitely pass this off as crucial feedback to the respective teams.

Do you know that even if you forget the Card Reader in mobile device settings, pair with the app, force close the app your device will connect again!

Thus requiring the need to constantly forget the reader.
definitely sounds like a nightmare

reef sleet Jan 21, 2022, 6:29 PM

#

I have sent an email to Nathan today so this is in the pipeline, just needed to get to a resolution fast!

simple hollow Jan 21, 2022, 6:31 PM

#

Hello! I'm taking over and getting caught up now. About that last part... are you saying once your app connects to a Terminal reader via Bluetooth and then your app is terminated the reader will show up as connected in Settings > Bluetooth?

reef sleet Jan 21, 2022, 6:31 PM

#

not all the time but yes it is happening

#

Hi Rubeus!

#

That was rude of me, sorry!

simple hollow Jan 21, 2022, 6:33 PM

#

No worries!

#

Does this only happen when the reader was previously connected/paired via the Settings app, or does it happen even if the reader was never paired via the Settings app?

reef sleet Jan 21, 2022, 6:33 PM

#

So interestingly I am debugging as we speak and my device seems to not be doing it. But early today this was an issue, subsequently, users just love to connect via Bluetooth.

As mentioned this is coming into our support constantly, and when you are trying to explain that you need to go to bluetooth and forget device etc it's not exactly a great experience

#

Surely we can come to a resolution in the SDK to see that you are connected to a reader already and pass it back in the SDK. Apps might need to register the Bluetooth Protocol String, but that's the price you pay right?

simple hollow Jan 21, 2022, 6:35 PM

#

Gotcha. Yeah, I think what you're describing is someone choosing to disconnect from the reader instead of forget it in the Settings app.

reef sleet Jan 21, 2022, 6:35 PM

#

Ok it has just happened to me again, Bluetooth device settings just paired with the card reader, had to leave for 5 minutes before turning the reader back on

simple hollow Jan 21, 2022, 6:37 PM

#

If you turn the reader off completely does it still show up in the Settings app?

reef sleet Jan 21, 2022, 6:38 PM

#

It shows in the settings as not connected

#

I am just trying to screen record

simple hollow Jan 21, 2022, 6:38 PM

#

Yeah, so it needs to be removed completely.

#

If you tap on the info button (i) you should have an option to forget the device.

reef sleet Jan 21, 2022, 6:38 PM

#

But it's there from connecting through the app

simple hollow Jan 21, 2022, 6:39 PM

#

Let me pull out my WisePad 3 and see if I can reproduce, it's been a while since I used that device...

#

Need to charge it a bit, hang on...

reef sleet Jan 21, 2022, 6:41 PM

#

Steps to take:

Find reader in Settings
Press i and forget device
Open app and discover device (Using SDK)
Turn on device
Connect to reader (Using SDK)
Force quit app, which kills SDK and reader disconnects
Go to Settings and the reader will be there

#

I am screen recording and of course, it is not doing it now, but if you leave the Bluetooth screen open with nothing using your SDK open it can auto-reconnect.

#

Ok I can't replicate the reconnect via settings at the moment.

#

Would you be able to provide us with the Bluetooth Protocol String so I can add to our plist under UISupportedExternalAccessoryProtocols - thus allowing us to check and tell the user in app to go and forget device?

simple hollow Jan 21, 2022, 6:50 PM

#

Let me look into that...

reef sleet Jan 21, 2022, 6:50 PM

#

Much better experience than them getting confused and contacting support in an irate manner! lol

reef sleet Jan 21, 2022, 6:52 PM

#

simple hollow Let me look into that...

Thanks

simple hollow Jan 21, 2022, 6:59 PM

#

I think the value would be com.bbpos.bt.wisepad, but I'm trying to find confirmation. I also don't think doing this is something we recommend, but it's certainly an interesting approach!

reef sleet Jan 21, 2022, 7:06 PM

#

Having this I can use this to check if they have connected via the wrong route and prompt them EAAccessoryManager.shared().connectedAccessories

#

Thanks will test see I can get something out of it

#

Didn't come up with anything with com.bbpos.bt.wisepad

simple hollow Jan 21, 2022, 7:18 PM

#

I've been looking around and can't find confirmation of that value. This isn't something that's ever come up before and thus isn't something we've explored.

reef sleet Jan 21, 2022, 7:18 PM

#

We must have clever customers!

#

All the way through development we never saw anything, but we connect via the app.

#

Also noticed that if you forget the device and then try and connect through settings, it says you can't.

#

But once it is paired you can, this is not an issue on Android luckily

simple hollow Jan 21, 2022, 7:21 PM

#

Can you include more prominent pairing instructions in your app? Or maybe even include instructions that ship along with the Terminal readers?

reef sleet Jan 21, 2022, 7:30 PM

#

Just designed!

#

Thanks for your help this evening

#

Much better than an email

#StillTrickie-terminal-sdk-ios