"Choose how to confirm it's you": the first step of a navigation challenge,
where the person picks the channel Instagram sends the security code over —
SMS or email. Instagram names the step select_verify_method, or
select_contact_point_recovery when the account's contact points are being
recovered; both are one screen. The step's own step_data suggests which
contact points exist (phone_number, email, choice), and a masked
contact point is what the app shows next to each choice. The person may also
be sent here after confirming a contact-point change.
Reached only over the screen a request was interrupted on: the platform's
challenge entry (OpenChallenge(error)) brings this screen as an
interruption, so it has no back and is no step of a trail. How one arrives
is always a server challenge on a request of the process — never an edge of
another screen.
Its one action, chooseVerificationMethod(method), takes the channel as the
typed option the step's data offers ('sms' or 'email'), sends the choice
to the step's challenge action unchanged ('0' for SMS, '1' for email) and
continues into the step the server answers with — usually the code entry
(ChallengeVerifyCodeScreen), sometimes the phone entry, and the challenge's
end when the answer is a close. A step the library does not model is
ChallengeStepNotModelledError, and the interrupted screen comes back first.
The action runs only while this screen is on top.
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 method choice
would settle what the screen shows and what the app sends on each choice.
"Choose how to confirm it's you": the first step of a navigation challenge, where the person picks the channel Instagram sends the security code over — SMS or email. Instagram names the step
select_verify_method, orselect_contact_point_recoverywhen the account's contact points are being recovered; both are one screen. The step's ownstep_datasuggests which contact points exist (phone_number,email,choice), and a masked contact point is what the app shows next to each choice. The person may also be sent here after confirming a contact-point change.Reached only over the screen a request was interrupted on: the platform's challenge entry (
OpenChallenge(error)) brings this screen as an interruption, so it has nobackand is no step of a trail. How one arrives is always a server challenge on a request of the process — never an edge of another screen.Its one action,
chooseVerificationMethod(method), takes the channel as the typed option the step's data offers ('sms'or'email'), sends the choice to the step's challenge action unchanged ('0'for SMS,'1'for email) and continues into the step the server answers with — usually the code entry (ChallengeVerifyCodeScreen), sometimes the phone entry, and the challenge's end when the answer is a close. A step the library does not model isChallengeStepNotModelledError, and the interrupted screen comes back first. The action runs only while this screen is on top.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 method choice would settle what the screen shows and what the app sends on each choice.