Today the drive engine uses the largestChangeId to track when a users corpus has changed and we need to fetch updates from the server.
However, this is problematic because
a) It doesn't work with team drive changes, which rely on a start page token, and
b) It's deprecated.
As it is desirable to have the same code flow to retrieve changes to the users corpus as well as team drives we should move to the new method.
This involves replacing "AboutResourceLoader" with something that works for multiple team drive ID's and caches the start page token as well.
Comment 1 by sashab@chromium.org
, Apr 19 2018