1.7 KiB
1.7 KiB
PDIAP-15765 - AO DOB field error not showing investigation
Status
- Holding
- Ready for closure timing review
Context
- This ticket is tied to an AO DOB validation issue.
- The issue was confirmed in the
TeenIdentityCheckflow for authenticated users.
Confirmed Findings
- 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,
CheckIdentitywas already correct. TheTeenIdentityCheckissue had two config gaps insidevalidation-rules: the root key should bevalidations, and the age gate also needseighteenOrAbovethere when that rule is required. - Follow-up validation on April 13 showed two distinct authenticated scenarios rather than one uniform cross-platform issue.
- A
HybridBrokeragescenario reproduces on both iOS and Android. - A Youth-flow
TeenIdentityCheckscenario 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-rulesstructure.
Current Guidance
- Treat the iOS-only Youth-flow discrepancy as the main client-side issue currently aligned with the story.
- Keep the cross-platform
HybridBrokeragescenario 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
TeenIdentityCheckand auth context.
Next Step
- Jeff approved moving the story to Done once the new sprint starts.