When initialized, chromeos::StartupAppLauncher (used to run kiosk app installation and launch) first attempts to load oauth credentials from a local file and inject it into the profile's token service.
Unless there is a valid use case for this, which I might be missing, we should simplify StartupAppLauncher and remove code for this. Worst case, we should add some metrics to confirm whether this is not currently used in production.
xiyuan@ - do you know if there is a reason to keep this around (I remember you tolling me some time ago that support for this file can safely be removed, but I wanted to double check).
Comment 1 by xiy...@chromium.org
, Dec 19 2017