The youth-regulation screen action. Its per-action QPL ids are issued by the
pcd response and the app chains them back verbatim, but unlike prefill /
oauth / send_login the action is not present in every pcd response (it is
only issued when the login home is youth-gated), so the result is optional.
When the response carries the action more than once (the AVD capture issues
it three times), the app chains the last instance, so the selector takes
the last matching candidate rather than the first.
The youth-regulation screen action. Its per-action QPL ids are issued by the pcd response and the app chains them back verbatim, but unlike prefill / oauth / send_login the action is not present in every pcd response (it is only issued when the login home is youth-gated), so the result is optional.
When the response carries the action more than once (the AVD capture issues it three times), the app chains the last instance, so the selector takes the last matching candidate rather than the first.