"You submitted an appeal": the UFAC flow's awaiting-review notice, shown
while the server reviews the identity-verification the person sent. The screen
keeps the UFAC state accumulated so far; its poll derives its parameters from
it, exactly as the legacy screen did.
Reached only as an interruption of a request (OpenChallenge(error)), usually
after the authenticity wizard's review started; it has no back and is no
step of a trail.
Its one action, checkReviewStatus(), is one tick of the awaiting-review poll. While the
answer still names the review screen it answers { status: 'still-waiting' }
and leaves this screen on top; the caller decides the pace, exactly as the
two-factor checkApproval() asks. Once the answer is no longer the review, it
continues into that step — the flow's thanks screen or the challenge's end.
A missing piece of the accumulated state is the existing typed
UfacAwaitingReviewMissingStateError, and a payload the library does not model
is ChallengeStepNotModelledError. The action runs only while this screen is
on top; the interrupted action is never retried.
Ships without a screenshot: the old class had none.
Unverified by recording. No recording of the Android 451 app on this step
exists, and the challenge module has no sample of this step in the library's
own sources. A recording of the Android app on the awaiting-review notice
would settle the page and the poll.
"You submitted an appeal": the UFAC flow's awaiting-review notice, shown while the server reviews the identity-verification the person sent. The screen keeps the UFAC state accumulated so far; its poll derives its parameters from it, exactly as the legacy screen did.
Reached only as an interruption of a request (
OpenChallenge(error)), usually after the authenticity wizard's review started; it has nobackand is no step of a trail.Its one action,
checkReviewStatus(), is one tick of the awaiting-review poll. While the answer still names the review screen it answers{ status: 'still-waiting' }and leaves this screen on top; the caller decides the pace, exactly as the two-factorcheckApproval()asks. Once the answer is no longer the review, it continues into that step — the flow's thanks screen or the challenge's end.A missing piece of the accumulated state is the existing typed
UfacAwaitingReviewMissingStateError, and a payload the library does not model isChallengeStepNotModelledError. The action runs only while this screen is on top; the interrupted action is never retried.Ships without a screenshot: the old class had none.
Unverified by recording. No recording of the Android 451 app on this step exists, and the challenge module has no sample of this step in the library's own sources. A recording of the Android app on the awaiting-review notice would settle the page and the poll.