fidelity-ai-workspace/ai/logs/2026-04-16.md

2026-04-16

Mattermost

• Jeff clarified that PDIAP-15765 should not move to Done until the PR is merged.
• Santosh approved the PR, but one code-owner approval is still required before merge.
• Jeff asked for one more AO working-group Teams reply that:
  • summarizes that the original iOS issue was reproduced and addressed with the iOS-side change
  • points the group to the Jira comment, Discourse comment, and PR
  • explains that the initially found HybridBrokerageAccountOpening / JointIdentityCheck problem is separate
  • notes which service-side changes were already made and which still appear to be needed
• David clarified that the confirmed service-side change was limited to the Youth-flow TeenIdentityCheck path. For external communication, avoid overstating the scope or calling out Rashmi by name unless that attribution is specifically needed.
• David clarified that the iOS change should be described as a compatibility improvement to reduce similar future issues with the older birthDate format. It should not be described in a way that implies it also applies to the separate HybridBrokerageAccountOpening / JointIdentityCheck issue.
• Jeff said the AO working-group draft was still confusing and wanted to edit it himself to make it very clear and avoid follow-up questions.
• David clarified that the HybridYouthAccountOpening / TeenIdentityCheck issue was iOS-only; it should not be described as affecting both iOS and Android.
• David clarified that the service-side change and the iOS-side fallback address the same Youth / TeenIdentityCheck issue, not two separate Youth issues. The service change was the immediate resolution, while the iOS PR is a compatibility safeguard if that older birthDate format appears again.
• David has personally seen birthDate used on two pages so far, but broader reuse in other flows is still unconfirmed and should be described carefully.
• For Jeff's framing question, the current understanding is two affected flow scenarios, not three: the iOS-only Youth / TeenIdentityCheck issue, and the separate cross-platform HybridBrokerageAccountOpening / JointIdentityCheck service-side issue.
• Jeff confirmed on April 15 that the minimal iOS birthDate fallback is the right change for the Youth / TeenIdentityCheck case and approved opening the PR under the same story.
• Jeff clarified the historical reason for the fallback behavior: older AO services often still use older payload conventions, while the SwiftUI refactor was validated more heavily against newer Slate-based services using validations.
• Jeff said the easiest fix is usually this kind of iOS-side fallback when the consumer is AO, the issue is iOS-only, and the service payload shape differs from what the SDK expects.
• Jeff approved the Jira and Discourse comments with one wording change: say I checked the original iOS issue again instead of I re-checked.
• Jeff approved sending a final AO working-group summary, but wanted it to be much clearer about what was fixed on iOS, what Rashmi changed on the service side, and what separate service-side issue still remains in HybridBrokerageAccountOpening / JointIdentityCheck.
• David later checked Cogstore and confirmed Rashmi's service change is already in QA as version 0.0.142, while production is still on 0.0.133, so that change is not live in production yet.
• Jeff concluded there is no point relying on a separate service release for the Youth issue if it would also require its own rollout; the iOS PR should be treated as the primary fix path, while the QA-side service change explains why the issue no longer reproduces in XQ1.