Non-registered readers calling didUpdateConnectedDevices with Basic SDK

[MalikParticipant]

Hi Flomies,
I stumbled upon a weird behavior with the Basic SDK. It’s not really affecting us per se but thought you might want to look into it.
If an application is using the Basic SDK and you have two NFC Readers A & B (where A is a registered reader with your servers and B is not), the steps mentioned below result in a behaviour that, in my opinion, should not happen.
1 – Turn on A, it will fire didUpdateConnectedDevices and connect the device. [OK]
2 – Turn on B and it will connect the peripheral but not fire didUpdateConnectedDevices. [OK]
3 – Turn off B at this point and it WILL fire didUpdateConnectedDevices. [PROBLEM]

Not only does it fire the didUpdateConnectedDevices method, but if you were to log the device’s serial number, you will see that it is firing that method as A. This means that even though A should still be connected, the SDK will consider it to be disconnected.

[RichardKeymaster]

Hi Malik, thanks for pointing this out. We’ve been lax about our auditing efforts to make sure customers abide by our licensing rules mainly because we’re focused on growing our offering and community. In an effort to address auditing issues and the like we are shifting our business model and licensing to something simpler. This required re-engineering our entire process a bit so have yet to announce the change though. Should be done sometime this summer.

best,
Richard

[Author]

Posts