GitLab

With this patch TrustedVaultClient.Backend has the ability to notify
native code that the keys in the vault may have changed. This
notification makes its way via TrustedVaultClientAndroid to ultimately
SyncServiceCrypto, where refetching logic is triggered.

This is expected to be an effective means for resolving encryption
issues transparently without user action and without having to restart
the browser.

The very same method is also used upon relevant user action such as
triggering the retrieval flow, in case the keys within the vault have
changed since the last fetch (e.g. if the backend failed to or does not
support broadcasting change notifications).

Bug: 1012659
Change-Id: I985db773fe5b18f107a8c8731d31dbd80aaf599c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1978005Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#730147}