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/06-daily/2026-04-17.md
View File

@@ -52,6 +52,13 @@ tags:
- The conflict appears to come from `FTAccountOpen` and `FTTransfer` depending on XFlowViewMaker with constraints that do not yet allow the new version.
- David noted that Tauf has handled similar cases before by updating the constraint directly in the podspec repo.
- Jeff asked David to message Tauf, ask him to remind David what he does in this case, and then document the process for future reference.
- Follow-up Teams evidence from Tauf clarified the practical fix path:
- first try `pod install`
- if resolution still does not move to the latest XFlowViewMaker version, the change belongs in the podspec repo, not in FTFrameworks
- `FTAccountOpen` and `FTTransfer` do not appear to hold a direct XFlowViewMaker version reference in their FTFrameworks source podspec files; the effective versioning is handled through the published podspec layer and the `ftAdapter` function
- David later clarified the actual fix: in the podspec repo PR, he removed the XFlowViewMaker version reference from both the latest `FTAccountOpen` and `FTTransfer` podspecs
- Tauf approved that podspec-repo PR
- After that merge, `pod install --repo-update` worked in Fid4 because the published podspecs no longer constrained the XFlowViewMaker version
## Communication Correction