com.bloks.www.bloks.caa.reg.tos, the terms and policies screen with the
"I agree" button — as the fresh-install Android 429 app sends it.
The accepted-username answer pushes it, so its enter sends nothing. Its
action agree() creates the account (create.account.async with the
session's context and attestation nonces) and answers the server's decision:
Created carries the created account and the screen the launch
leaves on top (the feed); ChallengeRequired carries the created account and
no launch, because the inactive-user answer sends the app into the
UFAC challenge, which is its own flow; PartiallyCreated is returned only
when the server issued no reg_info to complete with. When the partial
answer does carry reg_info, the action completes the account itself with
the slim completion and returns that answer. A launch failure after
the account exists is RegisteredButLaunchFailedError, which keeps the
created account; the screen stays on top for its other action,
retryLaunch(), which runs only the launch again — the same action after a
restored checkpoint, whose progress is the failed launch.
No screenshot: the frame needs a registration that reached this step.
Unverified on Android 451: this screen is modelled on 429 only. What
closes it is an Android 451 app registering a new account from the login
homepage.
com.bloks.www.bloks.caa.reg.tos, the terms and policies screen with the "I agree" button — as the fresh-install Android 429 app sends it.The accepted-username answer pushes it, so its enter sends nothing. Its action
agree()creates the account (create.account.asyncwith the session's context and attestation nonces) and answers the server's decision:Createdcarries the created account and the screen the launch leaves on top (the feed);ChallengeRequiredcarries the created account and no launch, because the inactive-user answer sends the app into the UFAC challenge, which is its own flow;PartiallyCreatedis returned only when the server issued noreg_infoto complete with. When the partial answer does carryreg_info, the action completes the account itself with the slim completion and returns that answer. A launch failure after the account exists isRegisteredButLaunchFailedError, which keeps the created account; the screen stays on top for its other action,retryLaunch(), which runs only the launch again — the same action after a restored checkpoint, whose progress is the failed launch.No screenshot: the frame needs a registration that reached this step.
Unverified on Android 451: this screen is modelled on 429 only. What closes it is an Android 451 app registering a new account from the login homepage.