39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
---
|
|
type: daily
|
|
project: fidelity
|
|
date: 2026-04-28
|
|
status: active
|
|
focus: [ao-discourse]
|
|
work-items: []
|
|
blockers: [phone-verification-gate-in-fttransferplayground]
|
|
tags:
|
|
- daily
|
|
- fidelity
|
|
updated: 2026-04-28
|
|
---
|
|
|
|
# 2026-04-28
|
|
|
|
## Focus
|
|
|
|
- Investigate the Discourse-reported FTTransfer / AccountLink reproduction path.
|
|
|
|
---
|
|
|
|
## 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.
|
|
|
|
---
|
|
|
|
## 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.
|