39 lines
1.2 KiB
Markdown
39 lines
1.2 KiB
Markdown
# PDIAP-15836 - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
|
|
|
|
## Status
|
|
|
|
- Approved
|
|
- Sequenced after `PDIAP-15838`
|
|
- Sized at `8` points
|
|
|
|
---
|
|
|
|
## Context
|
|
|
|
- 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.
|
|
|
|
---
|
|
|
|
## 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`.
|
|
- 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.
|
|
|
|
---
|
|
|
|
## 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`.
|