feat: Update work items and daily notes, closing completed tasks and prioritizing REST activation investigation on iOS

This commit is contained in:
2026-04-20 07:22:50 -06:00
parent dbc1894e27
commit 786a35f134
7 changed files with 82 additions and 32 deletions

View File

@@ -1,14 +1,14 @@
---
type: work-item
project: fidelity
status: active
status: done
ticket: PDIAP-15765
title: "AO DOB field error not showing investigation"
systems: [xflowsdk, xflowviewmaker, ftframeworks, fid4, cogstore]
workstreams: [ao-discourse, xflow-debugging, consumer-integration]
people: [jeff-dewitte, gurram-santosh, raj-sundararaj]
related: [pdiap-15838]
updated: 2026-04-17
updated: 2026-04-20
tags:
- work-item
- fidelity
@@ -19,10 +19,10 @@ tags:
## Status
- Active closeout
- Done
- Small XFlowSDK compatibility fix merged and released in XFlow `2.8.48`
- XFlowViewMaker was updated to the new XFlow version, approved, and published after the required code-owner approval
- The downstream Fid4 update is in progress through an open consumer PR
- The downstream Fid4 update was carried through a consumer PR that was later approved and merged
---
@@ -70,11 +70,11 @@ tags:
## Next Step
- The XFlowViewMaker approval and publish step are now complete.
- Resolve the Fid4 dependency conflict through the podspec repo by removing the XFlowViewMaker version reference from both the latest `FTAccountOpen` and `FTTransfer` podspecs.
- The XFlowViewMaker approval and publish step are complete.
- The Fid4 dependency conflict was resolved through the podspec repo by removing the XFlowViewMaker version reference from both the latest `FTAccountOpen` and `FTTransfer` podspecs.
- The podspec-repo PR was sent to Tauf and approved.
- After that merge, `pod install --repo-update` in Fid4 worked because the published podspecs no longer restricted the XFlowViewMaker version.
- A Fid4 PR with the latest versions is now open; continue with the consumer PR/review path now that dependency resolution is unblocked.
- After the Fid4 PR merges, treat the app release as the final downstream step before broader user visibility.
- The Fid4 PR with the latest versions was later approved and merged.
- Story moved to Done after the downstream release propagation completed.
- 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.