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

docs: update Discourse AccountLink investigation status and capture April 30 daily progress

Browse Source
This commit is contained in:
David Delagneau
2026-04-30 11:28:14 -06:00
parent fa1ab57de8
commit 5ceb3ec42e
3 changed files with 26 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
project-knowledge/06-daily/2026-04-29.md
View File

@@ -5,11 +5,11 @@ date: 2026-04-29
status: active
focus: [ao-discourse]
work-items: []
blockers: [phone-verification-gate-in-fttransferplayground]
blockers: []
tags:
- daily
- fidelity
updated: 2026-04-29
updated: 2026-04-30
---
# 2026-04-29
@@ -25,31 +25,37 @@ updated: 2026-04-29
- David successfully configured the `FTTransferPlayground` environment.
- For the version Zachary mentioned, David did not find a matching branch; the closest match found was the tag `Release/Foundation/5.0.0-beta.24`, assumed to correspond to the `5.0.24 beta` version Zachary referenced.
- David reached the flow so it now looks similar to Zachary's video, but the app asks for phone-number verification before the web view loads.
- David asked Zachary for reproduction details, including whether the issue reproduces in `Fid4` and which account/steps were used.
- With the account Zachary shared, David reproduced the issue in `FTTransferPlayground`.
- David tested the same account in `Fid4`, but the issue did not reproduce there.
- David narrowed the visible issue to the `BankInformationView` path rather than XFlow directly: an XFlow flow occurs before the web view is presented, but it finishes before `BankInformationView` takes over.
---
## Findings
- David does not yet know how to bypass the phone-number verification step in `FTTransferPlayground`.
- In prior `Fid4` validation, a similar step could be bypassed by enabling Face ID, but trying that in `FTTransferPlayground` produced a separate error that is not yet understood.
- The current follow-up may require asking Zachary which user he used or whether he knows what causes the Face ID / verification error in this app.
- The issue occurs when tapping `exit`: the alert appears, but the view immediately rebuilds.
- The behavior currently looks like a SwiftUI recomposition issue: `.state` is updated to `.loading`, which triggers a redraw, presents an `EmptyView`, dismisses the alert, and reloads the web view.
- The remaining uncertainty is why this happens in `FTTransferPlayground` but not in `Fid4`.
---
## Communication
- David updated Jeff with the `FTTransferPlayground` setup status and the current verification blocker.
- Jeff asked David to ping Zachary directly for help, including asking whether Zachary has seen the issue in `Fid4` and how David might reproduce it there.
- David reported that the issue reproduces in `FTTransferPlayground` with Zachary's account but not in `Fid4` with the same account.
- Jeff asked David to prioritize resolving the Discourse consumer issue by end of day on April 30 if possible.
---
## 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.
- Continue deeper testing to isolate why the behavior occurs in `FTTransferPlayground` but not in `Fid4`.
- Verify the root cause and whether there is any remaining relationship to XFlowViewMaker before assigning ownership or creating a story.
---
## Blockers
- Phone-number verification currently blocks reaching the web-view portion of the flow in `FTTransferPlayground`.
- None currently.