igpapi — Instagram private API Simulator for Node.js (API reference) 4.19.0
    Preparing search index...

    Variable RegistrationTermsOfServiceScreenConst

    RegistrationTermsOfServiceScreen: RegistrationTermsOfServiceDefinition = ...

    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 onboarding's profile card); 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.

    Verified on Android 453 by conformance.453/register-usa-number: the recording's own screen path, whose requests and order this screen sends. The scene ends at the create call's requests; the cold-start prelude is a declared precondition, and issue #966 closes the agree() drive.