Issue when disconnecting DS2278 scanner via SDK 2.6.25 - NullPointerException in BluetoothLEManager

T Tristan Delhez 23 hours 51 minutes ago
12 0 0

Hello,

Since upgrading to version 2.6.25 of the Zebra Android SDK, I have encountered an issue when calling the method:

Application.sdkHandler.dcssdkTerminateCommunicationSession(getScannerID());

The method returns a positive result (DCSSDK_RESULT_SUCCESS), confirming the disconnection. However, I get the following error during execution:

W/BluetoothGatt(15572): Unhandled exception in callback
W/BluetoothGatt(15572): java.lang.NullPointerException: Attempt to invoke interface method 'void com.zebra.scannercontrol.IDcsScannerEventsOnReLaunch.onScannerDisconnect()' on a null object reference
W/BluetoothGatt(15572): 	at com.zebra.scannercontrol.BluetoothLEManager.disconnectBleScanner(BluetoothLEManager.java:595)
W/BluetoothGatt(15572): 	at com.zebra.scannercontrol.BluetoothLEManager$4.onConnectionStateChange(BluetoothLEManager.java:621)
W/BluetoothGatt(15572): 	at android.bluetooth.BluetoothGatt$1$5.run(BluetoothGatt.java:363)
W/BluetoothGatt(15572): 	at android.bluetooth.BluetoothGatt.runOrQueueCallback(BluetoothGatt.java:1003)
W/BluetoothGatt(15572): 	at android.bluetooth.BluetoothGatt.-$$Nest$mrunOrQueueCallback(Unknown Source:0)
W/BluetoothGatt(15572): 	at android.bluetooth.BluetoothGatt$1.onClientConnectionState(BluetoothGatt.java:358)
W/BluetoothGatt(15572): 	at android.bluetooth.IBluetoothGattCallback$Stub.onTransact(IBluetoothGattCallback.java:135)
W/BluetoothGatt(15572): 	at android.os.Binder.execTransactInternal(Binder.java:1321)
W/BluetoothGatt(15572): 	at android.os.Binder.execTransact(Binder.java:1280)

I don't understand this error because, after reviewing the documentation, I couldn't find any indication that sdkHandler implements the IDcsScannerEventsOnReLaunch interface.

While the scanner does disconnect successfully, the problem occurs when I attempt to reconnect it immediately afterward. The connection is established, but the process does not complete, leaving me stuck on my connection screen. This issue did not occur in the previous SDK version.

Has anyone encountered a similar issue, or is there a recommended way to properly handle the scanner disconnection to avoid this problem?

Thanks in advance for your help!

CONTACT
Can’t find what you’re looking for?