Refresh access tokens for TiclInvalidationService

chrome/browser/invalidation/ticl_invalidation_service.cc

Index: chrome/browser/invalidation/ticl_invalidation_service.cc
diff --git a/chrome/browser/invalidation/ticl_invalidation_service.cc b/chrome/browser/invalidation/ticl_invalidation_service.cc
index ee2da37e8c620d76aadbbbd59df21dad82b69026..c47dfb77074eaa82f89ea3ef598f497e1bfd3465 100644
--- a/chrome/browser/invalidation/ticl_invalidation_service.cc
+++ b/chrome/browser/invalidation/ticl_invalidation_service.cc
@@ -258,7 +258,13 @@ void TiclInvalidationService::OnGetTokenFailure(
 
 void TiclInvalidationService::OnInvalidatorStateChange(
     syncer::InvalidatorState state) {
-  invalidator_registrar_->UpdateInvalidatorState(state);
+  if (state == syncer::INVALIDATION_CREDENTIALS_REJECTED) {
+    // This might not be a real auth error.  Our access tokens expire

[tim (not reviewing), 2013/07/30 21:01:00]

Maybe instead of "real", say  "This may simply be due to normal OAuth access
token expiration, which means we have to fetch a new one using our refresh
token."  And perhaps mention how the cycle is broken (?) in the event of a real
error?

+    // eventually.  Sometimes all we need to do is fetch a fresh one.
+    RequestAccessToken();
+  } else {
+    invalidator_registrar_->UpdateInvalidatorState(state);
+  }
 }
 
 void TiclInvalidationService::OnIncomingInvalidation(