Handle unbound service.
Previously, Assistant UI could only be launched via hotword. This meant it was impossible to see Assistant UI if the underlying service was not started. Now, there are non-hotword entry points wired up and it is possible to launch Assistant UI with the underlying service in an unready state. This can happen if the underlying service fails to get a token and bind itself to AssistantController, as happens when logging in without a network connection. Now we will show a toast. Just a generic message for now, need to get final text from UX. Bug: b:79752950 Change-Id: I48ae014e257db0012ac791be40f1245e5c3316b0 Reviewed-on: https://chromium-review.googlesource.com/1060603 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#559243}
Showing
Please register or sign in to comment