Closed emaxx-google closed 8 months ago
Some pointers:
check()
method).chrome.storage.local.get()
API) is at managed-registry.js in the same directory. That code already supports listening for the update notifications (see the chrome.storage.onChanged.addListener()
call); so the bug is only about this update notification not being delivered to the code that shows the dialog.
Currently, when the managed policy gets updated, it has no influence on the previous requests that are blocked waiting for user decision (i.e. until it presses "Allow" or "Block").
Instead, if the updated managed policy contains values that correspond to the previously attempted permission requests, they should become immediately resolved by the Connector app.
P.S. This issue produces problems mostly when running on the login screen: it may be that the applications will be installed and started before the actual value for the managed policy is received.