Application does not auto reconnect to scanner in SSI BT Classic mode

[mhieung]

Hi Zebra team,
I'm testing the app with DS3678 scanner connected via SSI BT Classic mode. The goal is for the app to reconnect with the scanner automatically when it becomes available after disconnection (the tablet/scanner is turned off, leave connection overnight, etc), just like it would in HID mode. However, I'm finding out that while it does attempt to reconnect, it does not reconnect successfully. Please help me check the issues and provide fixes if available.
Software version I'm using: versionName "2.6.22.0"
Java 17
Android 14, API 34
Gradle 8.2
Thank you!

[AlvaroZapp]

Hello,
I can confirm I’m experiencing the same problem with the Zebra RS6100 using SSI over BLE (tested with Scanner SDK for Android v2.6.29.0).

Flow I see:

1. First connection works fine (pairing via STC barcode).
2. Kill the app.
3. Relaunch the app → the SDK attempts to reconnect using the previously stored host-id.
4. The scanner reacts: it starts to beep repeatedly for ~20–30 seconds with the red LED blinking.
5. Finally, the connection fails. The SDK reports:

onConnectionStateChange → status=8 (GATT_INSUFFICIENT_AUTHORIZATION)  
newState=0 (disconnected)  
Bond state = BONDED (12)  

Important notes:

• This is not only happening in my own app: I downloaded and tested the official Zebra sample app from this repo, and the reconnection fails in exactly the same way.
• It happens consistently on RS6100 firmware R05 (and I also saw the same behavior with R09).
• The device clearly detects the reconnect attempt (beeps + red LED), but the session is rejected and the only workaround is to unpair + pair again via STC.

👉 This looks like a critical bug in the SDK or scanner firmware handling SSI BLE reconnections.
It completely blocks normal usage because every app restart forces the user to re-pair manually, which is not acceptable in production workflows.

Could you please confirm if this is a known issue, and if there is a fix or planned update?
This needs urgent attention, as it breaks the expected reconnection flow both in custom apps and in Zebra’s own sample.