You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Subscribers to permission changes will be notified unnecessarily if the new permissions for a subscribed RPC are exactly the same when an OnPermissionsChange notification is received. The sdl_filterPermissionChangesForFilters only checks for the rpcName and not the hmiPermissions and parameterPermissions.
When the OnPermissionsChange notification is sent, it includes all of the supported RPCs, not just the RPCs whose permissions changed. If the permissions for an RPC did not change, the observer will still be notified. This is because the permission manager assumes that the notification will only include the RPCs whose permissions changed.
This seems likely to be a Core bug.
Reproduction Steps
[Step 1]
[Step 2]
[Step 3]
Expected Behavior
[Some expected behavior]
Observed Behavior
[Some observed behavior]
OS & Version Information
iOS Version: n/a
SDL iOS Version: v5.2
Testing Against: [Ford] Sync Gen 3
The text was updated successfully, but these errors were encountered:
See #957
Bug Report
Subscribers to permission changes will be notified unnecessarily if the new permissions for a subscribed RPC are exactly the same when an
OnPermissionsChange
notification is received. Thesdl_filterPermissionChangesForFilters
only checks for therpcName
and not thehmiPermissions
andparameterPermissions
.When the
OnPermissionsChange
notification is sent, it includes all of the supported RPCs, not just the RPCs whose permissions changed. If the permissions for an RPC did not change, the observer will still be notified. This is because the permission manager assumes that the notification will only include the RPCs whose permissions changed.This seems likely to be a Core bug.
Reproduction Steps
Expected Behavior
[Some expected behavior]
Observed Behavior
[Some observed behavior]
OS & Version Information
The text was updated successfully, but these errors were encountered: