diff --git a/project-knowledge/01-current/current-work.md b/project-knowledge/01-current/current-work.md index d7c18a4..71653a7 100644 --- a/project-knowledge/01-current/current-work.md +++ b/project-knowledge/01-current/current-work.md @@ -15,10 +15,11 @@ tags: - Track REST migration findings - Debug Discourse and AO issues - Prepare better updates for the current manager or stakeholder through Mattermost -- Follow up on active tickets through `project-knowledge/02-work-items/`, especially `PDIAP-14859`, `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838` -- Wrap up `PDIAP-14859` by publishing the approved rollout document, linking the spike-result documents and follow-up story, then closing the spike -- After the immediate `PDIAP-14859` closeout and `PDIAP-15765` resume work, return to `PDIAP-15838`; `PDIAP-15836` comes later -- Finish `PDIAP-15765` propagation after the XFlow `2.8.48` release by carrying the already-published XFlowViewMaker update through the Fid4 PR and downstream consumer path +- Follow up on active tickets through `project-knowledge/02-work-items/`, especially `PDIAP-15838` and `PDIAP-15836` +- `PDIAP-15765` is done and `PDIAP-14859` is also done +- `PDIAP-15838` is now in progress +- The current top priority is investigating why REST is not activating on iOS +- `PDIAP-15836` comes after the current REST-investigation / Apollo-removal work - Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of `PDIAP-15765` scope unless later evidence proves it belongs there - Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers - Thoroughly verify current `ApexBridgingAddressComponent` / rule-loading usage before describing it as inactive or dead code @@ -35,7 +36,7 @@ tags: - When describing the XFlowSDK fallback PR, frame it as a compatibility improvement for similar future `birthDate` payloads, not as a fix for the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` issue - The Youth / `TeenIdentityCheck` issue was iOS-only; do not describe it as reproducing on both platforms - The service-side payload update and the XFlowSDK fallback PR address the same Youth / `TeenIdentityCheck` issue; do not split them into separate Youth issues when summarizing scope -- The `PDIAP-15765` compatibility fix is now merged and released in XFlow `2.8.48`; the XFlowViewMaker follow-up has also been approved, published, and unblocked in Fid4 through a podspec-repo change, and the current downstream step is the open Fid4 PR/update path +- The `PDIAP-15765` compatibility fix is now fully closed out and the story is in Done - A new urgent consumer report says REST calls fail on iOS when the toggle is enabled, but current local validation says REST works on both `main` and `release/4.30`; treat version/flag mismatch as the leading explanation until broader evidence says otherwise - Before closing out the AO thread, send one more working-group Teams reply that summarizes the original iOS issue, links the Jira comment, Discourse comment, and PR, and separates the remaining `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue - The `HybridBrokerageAccountOpening` / `JointIdentityCheck` rule-content issue appears unchanged between QA and Production in Cogstore and should be treated as the remaining service-side follow-up @@ -53,7 +54,7 @@ tags: - Keeping REST deprecation scope explicit while GraphQL fallback still exists - Current LaunchDarkly access does not include Flagship LD projects; only the sample app LD project is available from David's side - Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement -- Closing `PDIAP-14859` cleanly with the right links, blocker relationship, and feature-flag wording +- Investigating why REST is not activating on iOS before continuing broader REST-migration cleanup - Avoiding assumptions when comparing iOS and Android validation behavior; scenario-specific parity needs to be confirmed before reporting scope - Avoiding assumptions about legacy Apex/ApexKit paths; breakpoint evidence and helper usage both need to be reconciled before reporting ownership or replacement guidance - When ownership is still uncertain under production pressure, prefer rollback-plus-investigation framing over confident blame assignment to consumers diff --git a/project-knowledge/01-current/work-items.md b/project-knowledge/01-current/work-items.md index b43849f..67ee9b1 100644 --- a/project-knowledge/01-current/work-items.md +++ b/project-knowledge/01-current/work-items.md @@ -18,18 +18,10 @@ Update the per-ticket files first when scope, status, sequencing, or communicati ## Current -- `PDIAP-14859` - Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation - Detail: `project-knowledge/02-work-items/pdiap-14859.md` - Current note: the impact write-up is published, and the rollout document is approved for publication; update it to use the new flag name `xflow-swiftui-container-enabled` with a note that it will be added later during implementation, then publish and close out the spike with `Spike Results:` links. - - `PDIAP-15838` - Remove Apollo for iOS Detail: `project-knowledge/02-work-items/pdiap-15838.md` - Current note: approved at `8` points and next to work on; keep it separate from the UIKit-removal spike. + Current note: now in progress; the immediate priority is investigating why REST is not activating on iOS, then continue the broader Apollo-removal / REST-migration work. - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment Detail: `project-knowledge/02-work-items/pdiap-15836.md` Current note: approved at `8` points, rooted in the AccountLink dismissal sequencing investigation, and sequenced after `PDIAP-15838`. - -- `PDIAP-15765` - AO DOB field error not showing investigation - Detail: `project-knowledge/02-work-items/pdiap-15765.md` - Current note: the small XFlowSDK iOS `birthDate` compatibility fix was merged and released in XFlow `2.8.48`; the XFlowViewMaker follow-up is now approved and published. A downstream Fid4 dependency conflict was resolved through a podspec-repo update removing the XFlowViewMaker version reference from the latest `FTAccountOpen` and `FTTransfer` podspecs, and the current step is the open Fid4 PR so the change can propagate through the real app path. diff --git a/project-knowledge/02-work-items/pdiap-14859.md b/project-knowledge/02-work-items/pdiap-14859.md index 1681fec..4d04f33 100644 --- a/project-knowledge/02-work-items/pdiap-14859.md +++ b/project-knowledge/02-work-items/pdiap-14859.md @@ -1,14 +1,14 @@ --- type: work-item project: fidelity -status: active +status: done ticket: PDIAP-14859 title: "Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation" systems: [xflowsdk, xflowviewmaker, fid4, ftframeworks] workstreams: [xflow-swiftui-migration, consumer-integration] people: [jeff-dewitte, quy-mai] related: [pdiap-15836] -updated: 2026-04-16 +updated: 2026-04-20 tags: - work-item - fidelity @@ -19,9 +19,9 @@ tags: ## Status -- Active +- Done - Rollout draft prepared and sent to Jeff for review on April 13, 2026 -- Rollout document approved for publication; publish and close out the spike next +- Rollout document was approved, published, and the spike was later moved to Done --- @@ -29,7 +29,7 @@ tags: - Approved title: `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation`. - This work is currently framed in the workspace as a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately. -- The remaining deliverable is process-oriented, not just technical implementation. +- The process-oriented deliverable has been completed and the spike is closed. --- diff --git a/project-knowledge/02-work-items/pdiap-15765.md b/project-knowledge/02-work-items/pdiap-15765.md index 3d11f36..56f0684 100644 --- a/project-knowledge/02-work-items/pdiap-15765.md +++ b/project-knowledge/02-work-items/pdiap-15765.md @@ -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. diff --git a/project-knowledge/02-work-items/pdiap-15838.md b/project-knowledge/02-work-items/pdiap-15838.md index b890ea4..2d34f5e 100644 --- a/project-knowledge/02-work-items/pdiap-15838.md +++ b/project-knowledge/02-work-items/pdiap-15838.md @@ -1,14 +1,14 @@ --- type: work-item project: fidelity -status: active +status: in-progress ticket: PDIAP-15838 title: "Remove Apollo for iOS" systems: [xflowsdk] workstreams: [rest-migration] people: [jeff-dewitte] related: [] -updated: 2026-04-16 +updated: 2026-04-20 tags: - work-item - fidelity @@ -19,8 +19,8 @@ tags: ## Status -- Approved -- Next story to work on +- In Progress +- Current top priority within this story is investigating why REST is not activating on iOS - Sized at `8` points --- @@ -46,6 +46,7 @@ tags: - Do not frame this ticket as directly tied to the UIKit-removal spike. - Do not imply it is dependent on or part of dismissal-sequencing work. - Keep the migration framing explicit: REST remains behind a feature flag until otherwise confirmed, and GraphQL fallback context still matters when describing the overall migration. +- Treat the REST-activation investigation as the immediate priority before resuming broader Apollo-removal cleanup. --- diff --git a/project-knowledge/06-daily/2026-04-17.md b/project-knowledge/06-daily/2026-04-17.md index c57f5dd..82ef7f3 100644 --- a/project-knowledge/06-daily/2026-04-17.md +++ b/project-knowledge/06-daily/2026-04-17.md @@ -65,6 +65,8 @@ tags: - The remaining XFlowViewMaker code-owner approval was obtained from Tauf, allowing the release process to continue. - The XFlowViewMaker release was published successfully. - David then opened the Fid4 PR with the latest versions and planned to request reviews from Santosh and Tauf. +- Later the Flagship/Fid4 PR was approved and merged. +- David planned to move `PDIAP-15765` to Done after that downstream merge. ## Mattermost Refresh - Urgent REST Validation diff --git a/project-knowledge/06-daily/2026-04-20.md b/project-knowledge/06-daily/2026-04-20.md new file mode 100644 index 0000000..2dfce90 --- /dev/null +++ b/project-knowledge/06-daily/2026-04-20.md @@ -0,0 +1,54 @@ +--- +type: daily +project: fidelity +date: 2026-04-20 +status: active + focus: [rest-migration] + work-items: [pdiap-15838] +blockers: [] +tags: + - daily + - fidelity +updated: 2026-04-20 +--- + +# 2026-04-20 + +## Focus + +- Prioritize investigation into why REST is not activating on iOS. +- Continue `PDIAP-15838` with the investigation as the immediate focus. + +--- + +## Work Done + +- Moved `PDIAP-15765` to Done. +- Moved `PDIAP-14859` to Done. +- Updated `PDIAP-15838` to In Progress. + +--- + +## Findings + +- The immediate priority is no longer closeout work on the completed stories. +- The immediate priority is to investigate why REST is not activating. + +--- + +## Communication + +- + +--- + +## Next Steps + +- Investigate why REST is not activating on iOS. +- Continue `PDIAP-15838` from that investigation path. + +--- + +## Blockers + +- None currently.