GitLab

TrustedVaultClient::FetchKeys() has an asynchronous signature, but the
Android implementation (and the JNI bridge) adopted a synchronous
implementation prior to this patch.

In this proposal, the operation becomes non-blocking, based on:
1. The introduction of a dedicated Java->C++ API call, invoked when the
   operation completes.
2. The adoption of base.Promise in TrustedVaultClient.Backend, which is
   an idiomatic way to express that keys will eventually be read.

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