[CrOS Multidevice] ChromeProximityAuthClient: conditionally use DeviceSyncClient.
ChromeProximityAuthClient now uses either CryptAuthService 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 CryptAuthService 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. TBR=jhawkins@chromium.org Bug: 824568, 752273, 848956 Change-Id: If78959aa2a0ef6dc9433bca29649ab2d837114a1 Reviewed-on: https://chromium-review.googlesource.com/1102161 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#567546}
Showing
Please register or sign in to comment