"Is Your Profile Information Correct?": the navigation challenge's review of
the contact point Instagram has on file, shown when the account's email or
phone was changed. Instagram names the step review_contact_point_change;
the step's step_data carries the username, the email and the phone the app
shows.
Reached only as an interruption of a request (OpenChallenge(error)); it has
no back and is no step of a trail.
Its two actions are the button's two answers: confirmContactPoint() sends
'0' ("Yes, It's Correct") and rejectContactPoint() sends '1' ("No,
Secure My Account", which leads to the new-password step) to the step's
challenge action unchanged, and each continues into the next step — the
challenge's end when the answer is a close. Each runs only while this screen is
on top; the interrupted action is never retried.
Ships with screens.challenge.review-contact-point-change.jpeg, the screen as
the old class was observed on a test account; the contact point in the frame
was redacted before it was added.
Unverified by recording. No recording of the Android 451 app on this step
exists: the answer is the challenge module's own sample, whose contact point
was sanitised. A recording of the Android app on this review would settle the
screen's layout and both branches.
"Is Your Profile Information Correct?": the navigation challenge's review of the contact point Instagram has on file, shown when the account's email or phone was changed. Instagram names the step
review_contact_point_change; the step'sstep_datacarries the username, the email and the phone the app shows.Reached only as an interruption of a request (
OpenChallenge(error)); it has nobackand is no step of a trail.Its two actions are the button's two answers:
confirmContactPoint()sends'0'("Yes, It's Correct") andrejectContactPoint()sends'1'("No, Secure My Account", which leads to the new-password step) to the step's challenge action unchanged, and each continues into the next step — the challenge's end when the answer is a close. Each runs only while this screen is on top; the interrupted action is never retried.Ships with
screens.challenge.review-contact-point-change.jpeg, the screen as the old class was observed on a test account; the contact point in the frame was redacted before it was added.Unverified by recording. No recording of the Android 451 app on this step exists: the answer is the challenge module's own sample, whose contact point was sanitised. A recording of the Android app on this review would settle the screen's layout and both branches.