sdk says no terminal is connected, yet if you turn off the terminal, it fires the onUnexpectedReaderDisconnect event

[scottwilson312]

On Android.

If I'm connected to the reader, then rebuild the app in android studio, then call getConnectedReader, it returns null.

However if I try to call discoverReaders, it doesn't find anything

If I restart the terminal with a paperclip, then the onUnexpectedReaderDisconnect fires. At this point, discoverReaders can find the terminal.

How is it possible that getConnectedReader returns null, yet powering down the reader fires onUnexpectedReaderDisconnect. Surely if there is no connected reader, then it doesn't make sense that one can be disconnected!

Thanks for this library by the way. It's great!

[nprail]

That is strange behavior 🤔

To be clear, you connected to a reader and then restarted the app via Android Studio, correct?