New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 877559 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Make MultiDeviceSetup Service notify observers of Cryptauth syncs

Project Member Reported by hansberry@chromium.org, Aug 24

Issue description

MultiDeviceSetupClient::Observer::OnHostStatusChanged() does not notify observers in the event of a Cryptauth sync. This means that if a client uses MultiDeviceSetup as the primary way to retrieve a host device object, and the laptop is left open for ~28 days, that host device object will have stale BeaconSeeds. This will prevent BLE communication with that device.

This is an edge-case (requires leaving the laptop logged in and on for ~28 days), so it's not too high priority, AFAICT.
 
Labels: -Pri-3 M-70 Pri-2
This is an edge case, but I think we should still try to get it fixed before launch to ensure things are broken for users who don't shut down or log out of their session very often.
Labels: -M-70 M-71
Labels: -Pri-2 Pri-3
Components: -UI>ProximityAuth UI>Multidevice

Sign in to add a comment