Files

david.delagneau e4b39c4a9e refactor: update work item statuses and sprint planning details for PDIAP-15836 and PDIAP-12284

2026-05-05 16:09:48 -06:00

type, project, status, ticket, title, systems, workstreams, people, related, updated, tags

type

project

status

ticket

title

systems

workstreams

people

updated

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
Quy already moved this story into the next sprint (26Q2.6); leave it in To Do until the sprint starts on Thursday
Jeff confirmed David can start the actual implementation work now, but must not move the story to In Progress until Thursday
Sequenced after PDIAP-15838 source work, but merge/release is delayed until after REST-transition consumer validation
Sized at 8 points

This story came out of the AccountLink root 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.

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.

This story should come after PDIAP-15838.
PDIAP-12284 is the original UIKit-wrapping removal story and was reopened after rollback.
Current relationship to add/track in Jira: PDIAP-15836 is blocked by PDIAP-12284, because the UIKit removal needs to land for the lifecycle fix to apply. David still needs to validate whether any part of PDIAP-15836 can 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-12284 branch. Current estimate is roughly 90-100 days from 2026-05-05 unless Fidelity shortens the review windows.

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.