[CrOS Multidevice] Migrate ProximityAuthWebUIHandler to conditionally use DeviceSyncClient.
ProximityAuthWebUiHandler now uses either ProximityAuthClient or DeviceSyncClient to get remote device info or perform Cryptauth calls, depending on whether the chromeos::features::kMultiDeviceApi is enabled. Once the migration to DeviceSyncClient has been completed across all of Smart Lock, code that references ProximityAuthClient will be removed. This is one of many future CLs which are migrating Smart Lock to use DeviceSync Mojo API instead of directly using the CryptAuth API. I have manually verified the correctness of this change by verifying the output on chrome://proximity-auth. Bug: 824568, 752273, 848956 Change-Id: Ia6bf1666f631a79c2873df3745232b8a8152bc8e Reviewed-on: https://chromium-review.googlesource.com/1099050 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:Tommy Li <tommycli@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#567354}
Showing
This diff is collapsed.
Please register or sign in to comment