"Thanks for Providing Your Info", with its one "Done" button: the last screen
of the UFAC flow, after the person sent what the review asked for. The screen
keeps no server value, because it sends no request: the flow's payload named
it, and nothing is left to continue from.
Reached only as an interruption of a request (OpenChallenge(error)): the
challenge's classification fetched the UFAC controller before this screen
opened, so its enter sends nothing. It has no back and is no step of a
trail.
Its one action, close(), is navigation only: it closes the interruption and
answers the screen underneath (ChallengeClosed) or, when the challenge
interrupted the launch itself, the session snapshot
(ChallengeClosedBeforeLaunch). No request goes out; the interrupted action
is never retried.
Ships with screenshots/thanks-for-providing-info.webp, the screen as the
old class showed it on a test account.
Unverified against the app. The Android 451 app's behavior on this step
is not known, and the challenge module has no sample of this step in the library's
own sources — its test builds a payload carrying the screen's own text. Seeing the Android app on this screen would settle what "Done" sends.
"Thanks for Providing Your Info", with its one "Done" button: the last screen of the UFAC flow, after the person sent what the review asked for. The screen keeps no server value, because it sends no request: the flow's payload named it, and nothing is left to continue from.
Reached only as an interruption of a request (
OpenChallenge(error)): the challenge's classification fetched the UFAC controller before this screen opened, so itsentersends nothing. It has nobackand is no step of a trail.Its one action,
close(), is navigation only: it closes the interruption and answers the screen underneath (ChallengeClosed) or, when the challenge interrupted the launch itself, the session snapshot (ChallengeClosedBeforeLaunch). No request goes out; the interrupted action is never retried.Ships with
screenshots/thanks-for-providing-info.webp, the screen as the old class showed it on a test account.Unverified against the app. The Android 451 app's behavior on this step is not known, and the challenge module has no sample of this step in the library's own sources — its test builds a payload carrying the screen's own text. Seeing the Android app on this screen would settle what "Done" sends.
Guide: Challenges