The confirmation-code entry of the UFAC flow: the short code Instagram sent
to the contact point the person just set. The screen keeps one params set per
action — submit, change the contact point, resend — because the three name
three different UFAC methods, plus the UFAC state accumulated so far.
Reached only as an interruption of a request (OpenChallenge(error)), usually
as the next step of the same challenge after the contact-point prompt; it has
no back and is no step of a trail.
Its actions:
submitCode(code) posts the code to the step's contact_point.submit_code
action unchanged and continues into the next step — another UFAC screen or
the challenge's end;
resendCode() asks for a new code (contact_point.resend_code) and
continues into the payload the server answers with, which is the same step
with fresh issued values;
changeContactPoint() goes one step back to update the contact point
(contact_point.unset) and continues into that payload, usually the
contact-point prompt again.
A payload the library does not model is ChallengeStepNotModelledError. Every
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 code entry would settle
the page, the code and both other actions.
The confirmation-code entry of the UFAC flow: the short code Instagram sent to the contact point the person just set. The screen keeps one params set per action — submit, change the contact point, resend — because the three name three different UFAC methods, plus the UFAC state accumulated so far.
Reached only as an interruption of a request (
OpenChallenge(error)), usually as the next step of the same challenge after the contact-point prompt; it has nobackand is no step of a trail.Its actions:
submitCode(code)posts the code to the step'scontact_point.submit_codeaction unchanged and continues into the next step — another UFAC screen or the challenge's end;resendCode()asks for a new code (contact_point.resend_code) and continues into the payload the server answers with, which is the same step with fresh issued values;changeContactPoint()goes one step back to update the contact point (contact_point.unset) and continues into that payload, usually the contact-point prompt again.A payload the library does not model is
ChallengeStepNotModelledError. Every 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 code entry would settle the page, the code and both other actions.