Closed ashare80 closed 8 months ago
We are experiencing something very similar. For an out of the box reader, we can connect and start the update on 3.2.1, but on an upgrade to 3.3.0 and 3.3.1, we get stuck on connecting.
@ashare80 thanks for raising this, we've identified the issue and would be releasing a fix soon
@ashare80 thanks for raising this, we've identified the issue and would be releasing a fix soon
Thanks!!
This issue should now be resolved by SDK 3.4.0
Summary
Received new M2 devices and they hang on calls to connect via Bluetooth and USB. After
onConnectionStatusChange
event of "CONNECTING" there are no callbacks toReaderCallback
orReaderListener
. Only after disconnecting the reader by turning off or unplugging USB does the error callback get called with the exception.The last logs we see before it hangs an no more logs or callbacks occur are:
Downgrading to
3.2.1
resolves and the reader correctly connects and starts the required reader updateAndroid version
Android 11
Impacted devices (Android devices or readers)
M2
SDK version
3.3.0 and 3.3.1