1.8 KiB
1.8 KiB
type, project, date, status, focus, work-items, blockers, tags, updated
| type | project | date | status | focus | work-items | blockers | tags | updated | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| daily | fidelity | 2026-04-29 | active |
|
|
|
2026-04-29 |
2026-04-29
Focus
- Continue investigating the Discourse-reported FTTransfer / AccountLink reproduction path.
Work Done
- David successfully configured the
FTTransferPlaygroundenvironment. - 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 the5.0.24 betaversion 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
Fid4validation, a similar step could be bypassed by enabling Face ID, but trying that inFTTransferPlaygroundproduced 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
FTTransferPlaygroundsetup 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.