FloBLE Noir – CommunicationStatus always .disconnected

[MorganParticipant]

In didChangeStatus, the communicationStatus variable is always disconnected, even when the reader is clearly connected. Even setting off a two-second dispatch timer to check if the status changed after that method completed – it’s still disconnected.

This is causing me troubles, because I’m trying to diagnose my other problem, which is that when the reader times out due to inactivity, pressing the button on the reader causes it to reconnect to my app – but the app never gets any cardStatus or didFindTag callbacks ever again. Which is a bit of a huge problem! The reader times out after thirty seconds and there’s no way to disable it; and once the reader times out, it never reconnects to the device. There seems to be no way to convince it to do so short of force-quitting the app and restarting…

[ScottKeymaster]

Hi Morgan,

Thanks for bringing this to our attention. Very sorry for the inconvenience this has caused. I am looking into this issue and will have it fixed for the next release.

Scott

• This reply was modified 6 years, 4 months ago by  Scott.

[ScottKeymaster]

Hi Morgan,

Please see 3.0.3-beta3 in on the iOS SDK repository.

Scott

[MorganParticipant]

Thanks Scott – that’s fixed both issues.

However, I’m still not sure how, or even if it’s possible to stop the readers from sleeping. Sending wakeReader() commands on a repeating timer doesn’t seem to do anything; nor does using wakeReader() or startReader() when I get a (now accurate!) disconnected status in statusDidChange.

Is there some kind of keep-awake method that you guys use or recommend?

[Author]

Posts