The SDL SDK didn't inform the app the connection is disconnected

[AndreLee-2019]

Bug Report

The SDL SDK didn't inform the USB SDL app the connection is disconnected. This issue is hard to reproduce, but we have seen it 2~3 times.

When it happened, it will keep printing the logs below. But the USB SDL app didn't know the connection status.
03-25 14:25:58.323 5520 5760 W Sdl Router Service: Unable to send packet through alt transport, it was null
03-25 14:25:58.323 5520 5760 E Sdl Router Service: Can't send data, no transport of specified type connected

Reproduction Steps

1. Install a BT SDL app (Like HearMeOut) and one USB SDL sample app on a mobile device.
2. Connect the BT to the SDL supported HU.
3. Connect the USB cable to the SDL supported HU.
4. Turn off the HU.

Expected Behavior

The USB SDL sample app should receive the onDestroy event in SdlManagerListener.

Observed Behavior

The USB SDL sample app didn't receive the onDestroy event in SdlManagerListener.
And the status cannot recover even we unplug the USB cable.

OS & Version Information

• Android Version: Android 10 (Samsung Note9)
• SDL Android Version: 4.11.1
• Testing Against: Check if the USB SDK sample app can be informed of the disconnection event.

Test Case, Sample Code, and / or Example App

https://smartdevicelink.com/en/docs/android/master/com/smartdevicelink/managers/SdlManagerListener/

Attached the logs of these tags "Sdl Router Service", "SdlProxy", "SdlProtocol".
SDL_issue_logs.txt

[joeygrover]

1. You should updated to at least 4.12.2, and hopefully the latest release for all fixes. 4.11 will not receive new fixes.
2. Can you provide the full logs?
3. What USB sample app are you using specifically?
4. What Core/hardware are you connecting to?

[AndreLee-2019]

Hi Joey, thanks for your quick response!

1. Ok, we'll try it.
2. Yes, attached the full log.
   SDL_issue_Full_log.txt
3. Actually, we use an SDL navigation app we developed.
4. The HU uses the SDL core v4.5.2.