com.bloks.www.bloks.caa.reg.name.ig.and.soap, "What's your name?" — the full
name screen, as the fresh-install Android 453 app sends it (verified: the 453
sign-up scene, conformance.453/register-usa-number).
The accepted-birthday answer pushes it, so its enter sends nothing. The
person types their full name; submitName sends name_ig_and_soap.async on
graphql_www (the 453 wire) and moves to the username screen. A name the
server refuses is the typed RegistrationInvalidNameError.
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.
com.bloks.www.bloks.caa.reg.name.ig.and.soap, "What's your name?" — the full name screen, as the fresh-install Android 453 app sends it (verified: the 453 sign-up scene,conformance.453/register-usa-number).The accepted-birthday answer pushes it, so its enter sends nothing. The person types their full name;
submitNamesendsname_ig_and_soap.asyncongraphql_www(the 453 wire) and moves to the username screen. A name the server refuses is the typedRegistrationInvalidNameError.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 theagree()drive.