"Add your own birthday — Enter your age": the navigation challenge's birthday
step, which Instagram shows when the account's age must be confirmed.
Instagram names the step add_birthday; the step's step_data carries the
birthday the account already has, when it has one, and the message and
restrictions the app explains next to the field.
Reached only as an interruption of a request (OpenChallenge(error)), and
usually as the next step of the same challenge; it has no back and is no
step of a trail.
Its one action, submitAge(age), is the person's single submission though the
app sends three requests: the age-to-date resolver, the birthday setter, and
the challenge's own completion, which is then classified and continued into
the next step — the challenge's end when the answer is a close. The age is
the person's input; the request's shapes (including the timestamp and the
Bloks client context) are the existing module's, unchanged. The action runs
only while this screen is on top; the interrupted action is never retried.
Ships with screens.challenge.add-birthday.png, the screen as the old class
was observed on a test account.
Unverified by recording. No recording of the Android 451 app on this step
exists, and the old class's own note says its implementation was never tested
live; the answer is the challenge module's own sample. A recording of the
Android app on the challenge's birthday step would settle the screen and the
three requests.
"Add your own birthday — Enter your age": the navigation challenge's birthday step, which Instagram shows when the account's age must be confirmed. Instagram names the step
add_birthday; the step'sstep_datacarries the birthday the account already has, when it has one, and the message and restrictions the app explains next to the field.Reached only as an interruption of a request (
OpenChallenge(error)), and usually as the next step of the same challenge; it has nobackand is no step of a trail.Its one action,
submitAge(age), is the person's single submission though the app sends three requests: the age-to-date resolver, the birthday setter, and the challenge's own completion, which is then classified and continued into the next step — the challenge's end when the answer is a close. The age is the person's input; the request's shapes (including the timestamp and the Bloks client context) are the existing module's, unchanged. The action runs only while this screen is on top; the interrupted action is never retried.Ships with
screens.challenge.add-birthday.png, the screen as the old class was observed on a test account.Unverified by recording. No recording of the Android 451 app on this step exists, and the old class's own note says its implementation was never tested live; the answer is the challenge module's own sample. A recording of the Android app on the challenge's birthday step would settle the screen and the three requests.