PDIAP-15765 - AO DOB field error not showing investigation

Status

This ticket is tied to an AO DOB validation issue.
The issue was confirmed for authenticated users in the HybridYouthAccountOpening flow on the TeenIdentityCheck page.

The issue reproduces only for authenticated users based on the currently stored evidence.
Root cause was documented.
The original external report was incomplete.
For the config discussion, CheckIdentity was already correct. The TeenIdentityCheck issue had two config gaps inside validation-rules: the root key should be validations, and the age gate also needs eighteenOrAbove there when that rule is required.
Follow-up validation on April 13 showed two distinct authenticated scenarios rather than one uniform cross-platform issue.
A HybridBrokerageAccountOpening / JointIdentityCheck scenario reproduces on both iOS and Android.
A HybridYouthAccountOpening / TeenIdentityCheck scenario works on Android but fails on iOS.
Current evidence suggests Android is more flexible in how it decodes rule variations, while iOS is stricter about the expected validation-rules structure.
Later validation on April 15 showed the original HybridYouthAccountOpening / TeenIdentityCheck issue no longer reproduces once the payload uses validations instead of birthDate.
A minimal XFlowSDK fix was still prepared on April 15 so the iOS .apxDateSelect path also falls back to birthDate for a future release.

Treat the iOS-only HybridYouthAccountOpening / TeenIdentityCheck discrepancy as the main client-side issue currently aligned with the story.
Keep the cross-platform HybridBrokerageAccountOpening / JointIdentityCheck scenario separate until it is clear whether it is a service/config issue, a distinct bug, or an unreported rule-processing difference.
Keep the authenticated-user qualifier whenever this ticket is mentioned.
Do not describe it as a generic validation issue without the TeenIdentityCheck and auth context.
The originally reported Youth issue appears fixed immediately by the service-side payload update, but the XFlowSDK fallback PR should still be released so iOS handles the older birthDate format more safely.
The HybridBrokerageAccountOpening / JointIdentityCheck issue is different from the original Youth report: the rule content itself does not include ageRange or eighteenOrAbove, so that path still points to a service-side update rather than the same iOS parsing gap.

Get the small XFlowSDK compatibility PR reviewed and released.
Close the story with comments explaining that the immediate Youth issue was resolved on the service side and that the XFlowSDK fallback fix will be available in the next release.
Keep the separate HybridBrokerageAccountOpening / JointIdentityCheck scenario out of the client-fix scope unless later evidence proves it is part of the same issue.
Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after consumer confirmation.