Fix policy invalidator lifecycle bugs for Android.

chrome/browser/policy/cloud/user_cloud_policy_manager.cc

Index: chrome/browser/policy/cloud/user_cloud_policy_manager.cc
diff --git a/chrome/browser/policy/cloud/user_cloud_policy_manager.cc b/chrome/browser/policy/cloud/user_cloud_policy_manager.cc
index 1772f0350724d724b47dd31920c8723dc6d85f0c..69eb8da834ba6ad55db3850b5dd41c5977dec65b 100644
--- a/chrome/browser/policy/cloud/user_cloud_policy_manager.cc
+++ b/chrome/browser/policy/cloud/user_cloud_policy_manager.cc
@@ -35,8 +35,9 @@ UserCloudPolicyManager::~UserCloudPolicyManager() {
 void UserCloudPolicyManager::Connect(
     PrefService* local_state, scoped_ptr<CloudPolicyClient> client) {
   core()->Connect(client.Pass());
-  StartRefreshScheduler();
+  core()->StartRefreshScheduler();
   core()->TrackRefreshDelayPref(local_state, prefs::kUserPolicyRefreshRate);
+  StartInvalidator();

[Mattias Nissler (ping if slow), 2013/08/29 16:02:30]

So the signal the invalidator apparently needs to listen to would be "core
connected/disconnected" AFAICS, correct?

[Steve Condie, 2013/08/30 00:16:35]

Yes, these signals are now published by the CloudPolicyCore.

 }
 
 // static
@@ -50,6 +51,7 @@ UserCloudPolicyManager::CreateCloudPolicyClient(
 }
 
 void UserCloudPolicyManager::DisconnectAndRemovePolicy() {
+  StopInvalidator();
   core()->Disconnect();
   store_->Clear();
 }