Unauthorized app does not get unregistered.

[Nilesh-harman]

Hi,
We need help related to wrong app-id passed to SyncProxyTester app. It's an app revoked issue i.e. unauthorized app handling.
There is no implementation for unregistering the unauthorized app in this scenario.

Pre-conditions:

1. Vehicle ignition is ON
2. CTR is ON
3. Android device connected via BT

Error Path:

1. Set APP ID 2110975391 with SyncProxyTester
2. Try to select SyncProxyTester on SYNC.
3. HMI shows UserFriendlyMessage.

Observed behavior:
SyncProxyTester does not get unregister from HMI.

Expected behavior:
As per SDL integration guideline(#3.1.2) the app should unregister as "isAppRevoked: true"
From the sequence diagram#13.1.4.5, please refer the rpc flow below
1)HMI-->SDL: request of SDL.ActivateApp
2)SDL-->HMI: response of SDL.ActivateApp with "isAppRevoked: true"
3)SDL-->HMI: Notification of BasicCommunication.OnAppUnregistered
But there is no implementation for OnAppUnregistered for the step #3.

Note: Version used is SDL 4.2. Please let me know if you need any info.

Thanks.

[AKalinich-Luxoft]

@Nilesh-harman we think that SDL behavior is correct in this case. It should not unregister the application, but should not allow to activate it after that. We also have ATF scripts with the corresponding expectations.

Additionally, SDL core has a field "count_of_run_attempts_while_revoked" (and ATF script) in the statistics section of the policy table which is used to track the attempts of activation of the revoked app, which makes no sense if SDL will unregister revoked applications.

For that reason, we concluded that the SDL integration guideline itself is wrong and should be updated to reflect the proper core behavior.
See the following PRs with the changes:
smartdevicelink/sdl_atf_test_scripts#2606
smartdevicelink/sdl_hmi#634
smartdevicelink/generic_hmi#475
smartdevicelink/sdl_hmi_integration_guidelines#259

[iCollin]

Closed via the above PRs