Don't conflate ARC++'s "ready" with "installed"
A previous commit mistakenly conflated "ready" (an ARC++ concept) with "installed" (an App Service concept), or equivalently (in the App Service model), "ready to run". As a consequence, with the App Service enabled, ARC++ apps weren't shown in the app list UI for 5 or more seconds after log-in, as it waiting for the ARC++ connection to become "ready". This did not match the behavior with the App Service disabled. The App Service doesn't actually have to worry about ARC++'s readiness. For example, ArcApps::Launch (in App Service code) calls arc::LaunchApp in (ARC++ code), which already handles the "!app_info->ready" case: https://cs.chromium.org/chromium/src/chrome/browser/ui/app_list/arc/arc_app_utils.cc?q=app_info-%3Eready&l=277 BUG=826982 Change-Id: I79f8adc7a3c17dfa700e572494dc0a9e05b6f429 Reviewed-on: https://chromium-review.googlesource.com/c/1449431Reviewed-by:Dominick Ng <dominickn@chromium.org> Commit-Queue: Nigel Tao <nigeltao@chromium.org> Cr-Commit-Position: refs/heads/master@{#628545}
Showing
Please register or sign in to comment