david.delagneau
2a234701c5
- Updated work items with new statuses, notes, and dependencies: - `PDIAP-15838` moved to Done, draft PR remains unmerged. - `PDIAP-15836` status updated to backlog-ready, sequenced after `PDIAP-15838`. - `PDIAP-12284` reopened for UIKit removal, dependency for `PDIAP-15836`. - Added new backlog items: `PDIAP-11961`, `PDIAP-11962`, `PDIAP-11562`, `PDIAP-12226`, `PDIAP-12227`, `PDIAP-12228`. - Completed `PDIAP-16167`, documented findings in Confluence. - Created daily log for 2026-05-05 summarizing work item updates and backlog triage. - Added diagnostic script for workspace analysis.
3.2 KiB
3.2 KiB
type, project, status, ticket, title, systems, workstreams, people, related, updated, tags
| type | project | status | ticket | title | systems | workstreams | people | related | updated | tags | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| work-item | fidelity | backlog-ready | PDIAP-15836 | Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment |
|
|
|
|
2026-05-05 |
|
PDIAP-15836 - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Status
- Approved, but should not be moved to In Progress until the next sprint starts
- Jeff asked David to start working on the
PDIAP-15836/PDIAP-12284implementation path, with Jira status movement deferred until Thursday after lunch - Sequenced after
PDIAP-15838source work, but merge/release is delayed until after REST-transition consumer validation - Sized at
8points
Context
- This story came out of the
AccountLinkroot cause investigation. - It is tied to the dismissal sequencing problem found after UIKit removal in SwiftUI-only paths.
- The root cause document was updated and the revised wording was approved.
Approved Scope
- Modernize dismissal delegate lifecycle sequencing for pure SwiftUI flows.
- Cover the missing lifecycle contract where delegate callbacks can happen before the view is fully removed.
- Validate the change across affected SwiftUI flows rather than only in one narrow reproduction.
Sequencing And Dependencies
- This story should come after
PDIAP-15838. PDIAP-12284is the original UIKit-wrapping removal story and was reopened after rollback.- Current relationship to add/track in Jira:
PDIAP-15836is blocked byPDIAP-12284, because the UIKit removal needs to land for the lifecycle fix to apply. David still needs to validate whether any part ofPDIAP-15836can be implemented independently on the SwiftUI path. - It is aligned with epic
26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2). - If possible, it should use the same consumer-impact feature flag strategy as the broader UIKit-removal rollout.
- Expect a long-lived branch: after implementation, maintain the branch until consumer-testing approval. Jeff expects the GraphQL-removal branch to merge first after the REST validation period, then that branch should be merged into the
PDIAP-15836/PDIAP-12284branch. Current estimate is roughly 90-100 days from 2026-05-05 unless Fidelity shortens the review windows.
Communication Notes
- Keep the scope framed as lifecycle sequencing in a pure SwiftUI environment, not only as a symptom like multiple modal presentation.
- If mentioned externally, keep it separate from
PDIAP-15838. - The Confluence/root-cause document was updated to reflect that FTTransfer changes are not the primary need anymore.
- The primary recommendation is to adjust the dismissal handling/sequencing correctly in the hosting path.
- FTTransfer improvements can still be mentioned as a secondary improvement, but not as a required change to reproduce the same visual behavior.
- When explaining why code still remains, clarify that the spike identified and documented the root cause, but implementation changes have not yet been published.