david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: update daily logs for 2026-04-30; refine Discourse / FTTransfer investigation findings and root cause analysis

Browse Source
This commit is contained in:
David Delagneau
2026-05-04 07:16:14 -06:00
parent 4e8c018f83
commit 7f0de3658f
3 changed files with 61 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
project-knowledge/01-current/current-work.md
View File

@@ -2,7 +2,7 @@
type: current
project: fidelity
status: active
updated: 2026-04-30
updated: 2026-05-01
tags:
- current-work
- fidelity
@@ -50,6 +50,9 @@ tags:
- Current Discourse / FTTransfer findings point to the `BankInformationView` path rather than XFlow directly: XFlow appears to finish before `BankInformationView` takes over, and the web-view reload looks like a SwiftUI recomposition/state issue in the playground path
- Continue the Discourse / FTTransfer investigation to verify root cause and any remaining relationship to XFlowViewMaker before assigning ownership or creating a story
- Jeff asked David to try to resolve the Discourse consumer issue by end of day on April 30 if possible
- Deeper Discourse / FTTransfer analysis now points to presentation-layer SwiftUI identity/lifecycle churn around `BankInformationView` and `BankSetupWebView`: XFlow eventing appears to set shared consumer-observed state, but current evidence does not show it directly mutating view identity, host lifecycle, or alert state.
- The working non-XFlow route appears to avoid the issue because it bypasses the extra XFlow destination presentation layer and associated state-coupling surface, while the failing playground path keeps the alert/popup transition and cover lifecycle coupled in the same reactive chain.
- The next implementation direction for the Discourse / FTTransfer issue is a pure SwiftUI fix that decouples alert state from the cover identity chain, avoiding unnecessary UIKit dependencies
- 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