56 lines
1.8 KiB
Markdown
56 lines
1.8 KiB
Markdown
---
|
|
type: daily
|
|
project: fidelity
|
|
date: 2026-04-29
|
|
status: active
|
|
focus: [ao-discourse]
|
|
work-items: []
|
|
blockers: [phone-verification-gate-in-fttransferplayground]
|
|
tags:
|
|
- daily
|
|
- fidelity
|
|
updated: 2026-04-29
|
|
---
|
|
|
|
# 2026-04-29
|
|
|
|
## Focus
|
|
|
|
- Continue investigating the Discourse-reported FTTransfer / AccountLink reproduction path.
|
|
|
|
---
|
|
|
|
## Work Done
|
|
|
|
- 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.
|
|
|
|
---
|
|
|
|
## 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.
|
|
|
|
---
|
|
|
|
## Communication
|
|
|
|
- David updated Jeff with the `FTTransferPlayground` setup status and the current verification blocker.
|
|
|
|
---
|
|
|
|
## 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.
|
|
|
|
---
|
|
|
|
## Blockers
|
|
|
|
- Phone-number verification currently blocks reaching the web-view portion of the flow in `FTTransferPlayground`.
|