Blimp OAuth2 token retreival on application start up.

chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java

Index: chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java b/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java
index 229deff15cfccb787b2b3cec375b489803071936..1eb12c17572b79fffd5e8ce0b967764b08e66fed 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/ChromeActivity.java
@@ -932,8 +932,10 @@ public abstract class ChromeActivity extends AsyncInitializationActivity
         DownloadManagerService.getDownloadManagerService(
                 getApplicationContext()).onActivityLaunched();
 
+        // Create delegate object for Blimp, and start authentication flow.
         mBlimpClientContextDelegate = ChromeBlimpClientContextDelegate
                 .createAndSetDelegateForContext(Profile.getLastUsedProfile().getOriginalProfile());
+        mBlimpClientContextDelegate.getBlimpClientContext().getAuthToken();

[nyquist, 2016/08/05 17:05:07]

It feels more natural if this call was "connect()" instead, which then would
trigger the auth fetching code, which would lead to a call with a token to an
internal connect-method.

[xingliu, 2016/08/09 04:17:45]

Done, now it's connect(), and fixed the call site of this to a callback in
AccountTracker Serivce.

 
         super.finishNativeInitialization();
     }