The security-code entry of a navigation challenge: "Enter the security code",
or "Check your email" for the email variants. Instagram names the step
verify_code, verify_email, verify_email_code or verify_sms_code; all
four are one screen. The step's step_data carries the masked contact point
the code went to and the resend delay the app counts down.
Reached only as an interruption of a request (OpenChallenge(error)), and
usually right after the previous step of the same challenge replaced itself
with this one. It has no back and is no step of a trail.
Its actions:
submitCode(code) sends the code to the step's challenge action unchanged
and continues into the next step — the method choice again on a wrong code,
or whatever the server decides; the challenge's end closes back to the
interrupted screen. A wrong code is the existing typed
IgChallengeNavigationVerifyCodeInvalidCodeError (the server's text), not a
different screen.
resendCode() asks for a new code and answers undefined: the request
models no challenge step, so this screen stays in front and the person
types the code that arrives. The app's resend countdown is not modelled;
pacing is the caller's.
goBackToPreviousStep() is the in-challenge "back" the step offers (the
screen itself has no back): it sends the challenge's rewind action
unchanged and continues into the step the server answers with.
Every action runs only while this screen is on top. The interrupted action is
never retried: closing the challenge returns to the screen underneath, and
the caller takes that action again.
Ships without a screenshot: the old class had none.
Unverified by recording. No recording of the Android 451 app on this step
exists: the answers are the challenge module's own samples and its earlier
live runs. A recording of the Android app on the challenge's code entry would
settle the screen's text, the resend and the in-challenge back.
The security-code entry of a navigation challenge: "Enter the security code", or "Check your email" for the email variants. Instagram names the step
verify_code,verify_email,verify_email_codeorverify_sms_code; all four are one screen. The step'sstep_datacarries the masked contact point the code went to and the resend delay the app counts down.Reached only as an interruption of a request (
OpenChallenge(error)), and usually right after the previous step of the same challenge replaced itself with this one. It has nobackand is no step of a trail.Its actions:
submitCode(code)sends the code to the step's challenge action unchanged and continues into the next step — the method choice again on a wrong code, or whatever the server decides; the challenge's end closes back to the interrupted screen. A wrong code is the existing typedIgChallengeNavigationVerifyCodeInvalidCodeError(the server's text), not a different screen.resendCode()asks for a new code and answersundefined: the request models no challenge step, so this screen stays in front and the person types the code that arrives. The app's resend countdown is not modelled; pacing is the caller's.goBackToPreviousStep()is the in-challenge "back" the step offers (the screen itself has noback): it sends the challenge's rewind action unchanged and continues into the step the server answers with.Every action runs only while this screen is on top. The interrupted action is never retried: closing the challenge returns to the screen underneath, and the caller takes that action again.
Ships without a screenshot: the old class had none.
Unverified by recording. No recording of the Android 451 app on this step exists: the answers are the challenge module's own samples and its earlier live runs. A recording of the Android app on the challenge's code entry would settle the screen's text, the resend and the in-challenge back.