Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revoked app can be activated via device consent in EXTERNAL_PROPRIETARY #3580

Closed
jacobkeeler opened this issue Nov 18, 2020 · 2 comments
Closed
Labels

Comments

@jacobkeeler
Copy link
Contributor

Bug Report

In EXTERNAL_PROPRIETARY policy mode, if an app is revoked, it can still be activated by providing consent for the device. This activation results in the app being brought to the foreground whenever it is reconnected as well.

Reproduction Steps

Using SDL HMI

  1. app1 is revoked and connected, but device is not consented
  2. Select app1 from the app list, accept consent prompt for device, HMI sends SDL.OnAllowSDLFunctionality(true)
Expected Behavior

app1 is not activated via BC.ActivateApp from SDL Core

Observed Behavior

SDL Core sends BC.ActivateApp to HMI, HMI brings app to foreground (although app1 still has hmiLevel: NONE). BC.ActivateApp is also sent to the HMI when the app reconnects.

OS & Version Information
  • OS/Version: Ubuntu 18.04
  • SDL Core Version: 7.0.0
  • Testing Against: Android Test Suite app
@aderiabin
Copy link

Current issue is not regression one. It can be reproduced on SDL versions less than 7.0.

@ShobhitAd
Copy link
Contributor

Closed via #3592

@Jack-Byrne Jack-Byrne mentioned this issue Mar 18, 2021
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants