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

feat: Document resolution process for Fid4 dependency conflict and clarify XFlowViewMaker versioning in podspec repo

Browse Source
This commit is contained in:
David Delagneau
2026-04-17 11:22:22 -06:00
parent 01f0a6bd33
commit 926433aa13
5 changed files with 18 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
vault/02-work-items/pdiap-15765.md
View File

@@ -71,9 +71,10 @@ tags:
## Next Step
- The XFlowViewMaker approval and publish step are now complete.
- Resolve the new Fid4 dependency conflict caused by downstream `FTAccountOpen` / `FTTransfer` constraints that do not yet accept the published XFlowViewMaker version.
- Ask Tauf to remind David of the exact podspec-constraint fix path used in similar cases, then document that process for future reuse.
- After the dependency constraint issue is resolved, update the Fid4 Podfile in `ap010981-ios-flagship-app`, run `tuist generate -n` and `pod install --repo-update`, then open the consumer PR.
- Resolve the Fid4 dependency conflict through the podspec repo by removing the XFlowViewMaker version reference from both the latest `FTAccountOpen` and `FTTransfer` podspecs.
- The podspec-repo PR was sent to Tauf and approved.
- After that merge, `pod install --repo-update` in Fid4 worked because the published podspecs no longer restricted the XFlowViewMaker version.
- Continue with the consumer PR/update path now that dependency resolution is unblocked.
- After the Fid4 PR merges, treat the app release as the final downstream step before broader user visibility.
- Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of the client-fix scope unless later evidence proves it is part of the same issue.
- Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after consumer confirmation.