+Aseem from the CryptAuth team

We've inspected the logs at [1] which occur just after a sync occurs, and it seems that the value synced down from the back-end is false. Aseem, is there a recent back-end change which would cause this to occur?

[1] https://cs.chromium.org/chromium/src/components/cryptauth/cryptauth_device_manager_impl.cc?q=OnGetMyDevicesSuccess

+Ron from the CryptAuth team

It seems that we call ToggleEasyUnlock(true) during setup, then at some point later, this gets changed to false when we sync down.

This means that either:
(1) ToggleEasyUnlock(false) was called at some point.
(2) There's an error on the back-end which is syncing down "false" when it should sync down "true".

Is there a way to inspect server logs to determine whether (1) has occurred?

Yes.
Please open a buganizer bug and specify gaiaId and androidId.
We can only look at the past 7 days.

Which component should I file the bug in?

jmercay@: Don't worry about filing a bug - we're working with the CryptAuth team to take care of this.

Discussion moved to b/80542475, since this is not a Chrome issue.

Keeping open until the dependent bug is also closed out.

b/ issue is complete - there's a PM that needs to land. Can we close this? It's not a P0 at this point.