[CrOS Multidevice] Make EasyUnlockServiceRegular conditionally use DeviceSyncClient.
EasyUnlockServiceRegular 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 the last of other similar CLs which are migrating Smart Lock to use DeviceSync Mojo API instead of directly using the CryptAuth API. This CL also injects DeviceSyncClient into EasyUnlockServiceRegular, making Smart Lock rely entirely on DeviceSyncClient if chromeos::features::kMultiDeviceApi is enabled. I have manually verified that it works correctly by testing the following: 1. Setting up Smart Lock. 2. Using Smart Lock in the regular lock-screen manner. 3. Using Smart Lock in the login-screen manner. 4. Ensuring that notifications display at the correct time. 5. Turning off Smart Lock. 6. Ensuring that permits are correctly saved to prefs (the new model can't use the old way of grabbing the user's AccountId). TBR=jhawkins@chromium.org Bug: 824568, 752273, 848956 Change-Id: I3acc6dec46ff1ddc2875fbfe97261bb195a9494b Reviewed-on: https://chromium-review.googlesource.com/1102164 Commit-Queue: Ryan Hansberry <hansberry@chromium.org> Reviewed-by:Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#567769}
Showing
This diff is collapsed.
Please register or sign in to comment