commit 91e9f9175bcd4ced2d45e298e05655847bda3821
author Ryan Hansberry <hansberry@chromium.org> Thu Feb 21 01:56:36 2019
committer Commit Bot <commit-bot@chromium.org> Thu Feb 21 01:56:36 2019
tree d9ed16795728013e86b851b72f8bae5cee8654c3
parent 4a6a13b80a4ccb125c79e49d1f8e69a2d808c95a

Smart Lock: Clear stale ProximityMonitor on disconnect.

UnlockManager was previously holding onto a stale
ProximityMonitor from its first connection. That meant
that if a disconnection and subsequent new connection
occurred, the old ProximityMonitor, with an old reference
to the previous connection (represented as a ClientChannel
object) was used. This always resulted in a Smart Lock
failure for a second connection, and occasionally, a crash.

In order to correctly reset the ProximityMonitor object,
the way that it is called had to be refactored (remove
completely unneeded ScreenLockBridge logic), in order to
consolidate calls to one place.

Bug: 931929
Change-Id: I9b9a65ad0f0752d58d680623815ea60b5369c45c
Reviewed-on: https://chromium-review.googlesource.com/c/1479941
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#634011}