fidelity-ai-workspace/vault/06-daily/2026-04-16.md

type, project, date, focus, work-items, blockers, updated, tags

type	project	date	focus	work-items	blockers	updated	tags
daily	fidelity	2026-04-16	ao-discourse xflow-debugging	pdiap-15765		2026-04-16	daily fidelity

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 that the relevant flow-definition change tied to Rashmi's service update is already in QA as version 0.0.142, while Production is still on 0.0.133, so that flow 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 flow-definition change explains why the issue no longer reproduces in XQ1.
• Durable tooling/system note: in Fidelity flow work, Cogstore is the platform used to modify and publish many individual flow configurations, compare versions per flow, and check who/when a specific flow version was published to QA or Production. Slate was the newer consumer-side configuration tooling during the SwiftUI refactor, but Jeff believes it is now decommissioned.
• Additional tooling note: flow IDs are not guaranteed to exist in both Cogstore and Slate, so the active configuration source for a given flow should be verified instead of assumed.
• David confirmed that the HybridBrokerageAccountOpening / JointIdentityCheck flow-definition content is the same in QA and Production even though the versions differ (0.0.267 vs 0.0.263), so that separate rule-content issue should also be reproducible in Production.
• Jeff asked Rashmi to revert the Youth-flow service change so the iOS-side PR can remain the single fix path for that issue.
• David confirmed Rashmi reverted the QA change by publishing the earlier flow version, and local Fid4 validation with the iOS PR showed the birthDate-based validation now works as expected.
• Jeff's preferred external summary is now very explicit: we went back and fixed their original iOS-only issue on the iOS side, while the separate HybridBrokerageAccountOpening / JointIdentityCheck issue is a new service-side problem that still needs its own follow-up.
• The PDIAP-15765 PR later received final approval, was merged, and the release pipeline produced XFlow 2.8.48.
• After the XFlow release, David updated XFlowViewMaker to 2.8.48, opened the follow-up PR, and sent it for review so the fix can propagate through the consumer path.
• David also sent the final AO working-group update with links to the Jira story, Discourse ticket, and PR.