#Ronan - Terminal Connection
jovial path
iOS and WisePAD3 reader
slate basin
You're correct, discoverReaders should stop on its own once you connect to a reader, and as far as I know that behavior has not changed. Let me see if I can find anything... in the meantime is it possible anything change on your end that may be the cause? Did you upgrade the Terminal SDK to a new version? Change your code? Anything like that?
Also, what version of the Terminal SDK are you using?
jovial path
I've been checking that all day but can't find any change in our code which will have done this. We're currently on SDK v2.2.0
Is anytihng returned by the SDK when discoverReaders has stopped? Is there any method for stopping it explicitly? Is this when cancel would be appropriate?
slate basin
Yeah, the completion block will be called when the discovery process ends: https://stripe.dev/stripe-terminal-ios/docs/Classes/SCPTerminal.html#/c:objc(cs)SCPTerminal(im)discoverReaders:delegate:completion:
Actually, wait, will it...
I think either the delegate methods will be called or the completion block will be called, but not both. Not 100% sure though.
Is this something you can reliably reproduce?
If so I recommend posting an issue with reproduction code/steps to GitHub so the Terminal team can investigate the issue: https://github.com/stripe/stripe-terminal-ios/issues
jovial path
I can't stop reproducing it right now. I'm not 100% sure no changes in our code could've done it, more like 97%, but reverting to previously working commits still produced the same outcome. I think I need to keep looking at it before taking it further as an issue. I just wanted some clarity on how the discoverReaders process completes.
Thanks alot for the rapid replies Rubeus