The login home's "Forgot password" step: the app sends
caa.ar.search.prefill.async with the action the login home issued and the
answer pushes the account-recovery search screen (should_push_screen), with
the params the screen is fetched with. The screen is in front from this
answer on, so the navigation event belongs here, not to the step that loads
it.
The request's server_params carry the issued action's values reassembled
in the order the recording sends them (the action's own map is ordered
differently); the aac comes from the login home's process state, because the
recorded action's server_params carry none. Its client_input_params are
built from the device and that aac, as the app does. The username field is
the login home's form value at the tap (usernameInput, absent in the
recording because its form was blank).
Internal helper of the recovery screens; not exported from the package.
The login home's "Forgot password" step: the app sends
caa.ar.search.prefill.asyncwith the action the login home issued and the answer pushes the account-recovery search screen (should_push_screen), with the params the screen is fetched with. The screen is in front from this answer on, so the navigation event belongs here, not to the step that loads it.The request's
server_paramscarry the issued action's values reassembled in the order the recording sends them (the action's own map is ordered differently); the aac comes from the login home's process state, because the recorded action'sserver_paramscarry none. Itsclient_input_paramsare built from the device and that aac, as the app does. The username field is the login home's form value at the tap (usernameInput, absent in the recording because its form was blank).Internal helper of the recovery screens; not exported from the package.