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

feat: update daily logs and work items for 2026-04-29; refine Apollo removal strategy and address FTTransfer issue

Browse Source
This commit is contained in:
David Delagneau
2026-04-29 07:39:55 -06:00
parent d3c5d8f7de
commit fa1ab57de8
6 changed files with 99 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
project-knowledge/06-daily/2026-04-28.md
View File

@@ -3,9 +3,9 @@ type: daily
project: fidelity
date: 2026-04-28
status: active
focus: [ao-discourse]
work-items: []
blockers: [phone-verification-gate-in-fttransferplayground]
focus: [rest-migration, ao-discourse]
work-items: [pdiap-15838]
blockers: []
tags:
- daily
- fidelity
@@ -16,23 +16,30 @@ updated: 2026-04-28
## Focus
- Investigate the Discourse-reported FTTransfer / AccountLink reproduction path.
- Continue `PDIAP-15838` Apollo-removal work, especially clearing the remaining transitive `PicoSDK` dependency from `SampleApp`.
- Start investigating the new Discourse-reported FTTransfer / AccountLink issue after the draft PR is open.
---
## Findings
- David successfully configured the environment for `FTTransferPlayground`.
- The exact version Zachary mentioned was not available as a branch; the closest match found locally was the tag `Release/Foundation/5.0.0-beta.24`, which appears to correspond to the `5.0.24 beta` version he referenced.
- David was able to reach the flow so it matches Zachary's video more closely, but before the web view loads, the app requires phone-number verification.
- David does not yet know how to bypass that verification step in `FTTransferPlayground`.
- In prior `Fid4` validation, a similar gate could be bypassed by enabling Face ID, but the same attempt in this app currently produces a separate error.
- The current follow-up may require asking Zachary which user he used or whether he recognizes the Face ID / verification error in this app.
- For `PDIAP-15838`, David updated `SampleApp` to use a newer `PicoSDK` path that no longer brings Apollo transitively, so Apollo is removed from the sample app dependency path as well as the direct XFlow cleanup path.
- The `PicoSDK` update re-enabled the FGO and FidFolios flows for testing in `SampleApp`; without the update, the Pico endpoint fails.
- Jeff confirmed the `SampleApp` / `PicoSDK` update is in scope for `PDIAP-15838` because Apollo needs to be removed from the project, and the sample app should stay aligned with how Fid4 consumes Pico.
- David clarified that the `PicoSDK` update affects `SampleApp`, not the `XFlowSDK` production runtime directly, and aligns `SampleApp` with the newer Pico usage already present in Fid4.
- A draft PR for `PDIAP-15838 - Remove Apollo for iOS` was opened for internal review before sending to Bruce.
- Aylwing reviewed the draft PR and raised questions around intentional removal of the REST kill switch, `PicoSDKManager` initialization ownership, resolver availability, and async completion returning to the main actor.
- Jeff confirmed removal of the REST kill switch is intentional for permanent GraphQL deprecation, but the PR should merge only after the previous REST-toggle implementation has been QA-tested and active in production with REST enabled for all consumers for 30 days without issues.
- David confirmed `TransactionContextManager(resolver:)` handles Pico setup internally in `PicoSDK 4.3.18` through lazy resolver-based initialization, and the `SampleAppAuthDependencyResolver` is already available from the view model.
- David confirmed the resolver is an existing `XFlowSampleAppViewModel` property.
- David applied a minimal `PicoInterface` patch so the `Task` does not strongly capture `self` and both completion paths return through `MainActor.run`, making UI-state callers safer.
- After internal review, the next handoff is to send the draft PR link to Bruce.
- A new Discourse report came in around an AccountLink / FTTransfer multiple-presentation or web-view rewrite issue. Earlier UIKit-removal investigation had ruled out that change as the cause, but Zachary provided additional detail and believes it may still come from XFlow, so ownership needs careful reproduction before suggesting it is outside XFlow.
---
## Next Steps
- Keep trying to reproduce the FTTransfer / AccountLink issue through `FTTransferPlayground`.
- Determine whether the phone-verification step can be bypassed locally.
- If not, ask Zachary which user/account he used or whether he knows why the Face ID path errors in this app.
- Send the `PDIAP-15838` draft PR to Bruce after internal review is ready.
- Keep the `PDIAP-15838` PR in draft/review state until the REST production-readiness window is satisfied.
- Continue investigating the Discourse-reported FTTransfer / AccountLink issue and confirm reproduction/ownership before proposing a story or suggesting it is outside XFlow.