DiscoveryDelegate:didUpdateDiscoveredReaders called twice about stripe-terminal-ios HOT 3 CLOSED

On Wed, Jan 9, 2019 at 12:00 PM Troy Payne ***@***.***> wrote: This is being called twice for me. Once without hardwareInfo, deviceSoftwareVersion, and batteryLevel then again with all of this. Is this intentional? If not, can it just be returned once with all information? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#23>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AWBHcG5vxMrjNZdw-RG3Ml5BeFYVf1GXks5vBkpZgaJpZM4Z4HJj> .

On Jan 9, 2019, at 4:14 PM, Ben Guo ***@***.***> wrote: Hi Troy, Yes, this is expected behavior when you use the Bluetooth proximity discovery method. Under the hood, the SDK first discovers the reader via a BT scan, and calls didUpdateDiscoveredReaders the first time. To get metadata like batteryLevel, the SDK needs to connect to the BT device, after we call didUpdateDiscoveredReaders a second time. Your app should always expect that there may be multiple calls to didUpdateDiscoveredReaders. Hope that makes sense! Ben On Wed, Jan 9, 2019 at 12:00 PM Troy Payne ***@***.***> wrote: > This is being called twice for me. Once without hardwareInfo, > deviceSoftwareVersion, and batteryLevel then again with all of this. Is > this intentional? If not, can it just be returned once with all information? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#23>, or mute the > thread > <https://github.com/notifications/unsubscribe-auth/AWBHcG5vxMrjNZdw-RG3Ml5BeFYVf1GXks5vBkpZgaJpZM4Z4HJj> > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADQS1BruO7jQFAh--ajNskGbhmQOyWtbks5vBlvSgaJpZM4Z4HJj>.