42 lines
1.7 KiB
Markdown
42 lines
1.7 KiB
Markdown
# 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 `TeenIdentityCheck` flow 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, `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 `HybridBrokerage` scenario reproduces on both iOS and Android.
|
|
- A Youth-flow `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.
|
|
|
|
---
|
|
|
|
## Current Guidance
|
|
|
|
- Treat the iOS-only Youth-flow discrepancy as the main client-side issue currently aligned with the story.
|
|
- Keep the cross-platform `HybridBrokerage` 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.
|
|
|
|
---
|
|
|
|
## Next Step
|
|
|
|
- Jeff approved moving the story to Done once the new sprint starts.
|