[AA Direct Actions] Small bugfixes.
This change fixes the following small bugs: - the argument experiment_ids was not declared for the list_assistant_actions direct action. - there was no way for the caller to specify the user account to use for RPCs, like there is for AA in CCT, which could mean RPCs could fail with 401 in production if the user is not signed into Chrome. list_assistant_actions now has a new parameter for that. - AutofillAssistantPreferencesUtil.isAutofillAssistantSwitchOn() was checked too early, when creating direct action handler, that is, when creating the Activity. This meant that if it ever changed during the Activity's lifetime, the behavior would be incorrect. This change checks it for every call instead. - If, after showing the onboarding, AA couldn't start, we could end up in a state where the onboarding UI was still showing. To solve this, this change transfers control of the UI only once AA is started. If that doesn't happen, the default behavior of OnboardingController triggers, which is to dismiss the UI. Bug: b/138276953 Change-Id: Ibd6ea42c710dc95fb854eea57d5a0b64a585573d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1720711Reviewed-by:Jordan Demeulenaere <jdemeulenaere@chromium.org> Commit-Queue: Stephane Zermatten <szermatt@chromium.org> Cr-Commit-Position: refs/heads/master@{#681765}
Showing
Please register or sign in to comment