Don't try to update incessently when Shell APK version is out of date.

chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java

Index: chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java
index 3cff61d0a10b1c391df28970eef09eeaf45c5658..42ecd8b5ebc083b427f7c10d1421686ea12e993c 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkUpdateManager.java
@@ -287,7 +287,7 @@ public class WebApkUpdateManager implements WebApkUpdateDataFetcher.Observer {
 
         if (!ChromeWebApkHost.areUpdatesEnabled()) return false;
 
-        if (isShellApkVersionOutOfDate(info)) return true;
+        if (isShellApkVersionOutOfDate(info) && mStorage.shouldRequestShellApkUpdate()) return true;

[pkotwicz, 2017/04/04 22:29:57]

Can we remove this if(){} statement entirely? I think that it is OK to only
check updates every 3 days.

I think that your CL changes the logic to try updates every 2 days if the
ShellAPK is updated. A 2 day interval is very similar to a 3 day interval.

Of course, if the update frequency is relaxed, it is possible that a user needs
to wait for 30 days before getting an update. Right now the ShellAPK updates we
are making are non critical. Waiting for 30 days does not sound that bad

[Xi Han, 2017/04/05 17:19:09]

I think 3 day is also good, but we'd better not wait for 30 days for the shell
update.

 
         return mStorage.shouldCheckForUpdate();
     }