56 lines
5.0 KiB
Markdown
56 lines
5.0 KiB
Markdown
---
|
|
type: current-work-items
|
|
project: fidelity
|
|
status: active
|
|
updated: 2026-05-14
|
|
tags:
|
|
- current-work
|
|
- work-item
|
|
- fidelity
|
|
---
|
|
# Active Work Items
|
|
|
|
Use this file as the quick summary for active Jira-linked work.
|
|
|
|
Detailed ticket memory now lives under `project-knowledge/02-work-items/`.
|
|
|
|
Update the per-ticket files first when scope, status, sequencing, or communication framing changes materially.
|
|
|
|
## Current
|
|
|
|
- `PDIAP-15838` - Remove Apollo for iOS
|
|
Detail: `project-knowledge/02-work-items/pdiap-15838.md`
|
|
Current note: ticket moved to Done after external review feedback was addressed, but the draft PR stays unmerged. Keep the branch up to date with `main` until REST backend is live in production and REST toggles have been enabled for consumers for the required validation window; expected merge timing is at least 30 days out. May 13 follow-up validation succeeded on iOS after Raj enabled the production LaunchDarkly toggle for the specific production test user's MID.
|
|
|
|
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
|
|
Detail: `project-knowledge/02-work-items/pdiap-15836.md`
|
|
Current note: moved to In Progress on May 7. David found a possible minimal dismissal fix path that would not require removing `UIHostingController`, but Jeff directed David to do the dismissal/lifecycle work and `PDIAP-12284` UIKit-removal work in the same branch because both changes require consumer testing. A May 11 simulator log review suggests the tested SwiftUI-host path fires delegate/session-clear callbacks only after host-disappearance confirmation, but broader branch and consumer validation are still needed.
|
|
|
|
- `PDIAP-12284` - Remove UIKit wrapping from XFlow
|
|
Detail: `project-knowledge/02-work-items/pdiap-12284.md`
|
|
Current note: moved to In Progress on May 12 and should be handled with `PDIAP-15836` in the same branch. Quy confirmed both stories can remain In Progress together, so no immediate Jira restructuring is required. Current implementation direction is to avoid Fid4 per-flow host-mode mapping and instead evaluate XFlowViewMaker-owned global host-mode resolution, with SwiftUI as default and `UIHostingController` only as an explicit temporary fallback. May 12 implementation pass resolved earlier shape concerns with neutral enum names, `iOS-XflowUIKitHostEnabled`, SwiftUI default semantics, and `AnyView` removed from builder internals. Fid4 now compiles after manual dependency/build handling. May 13 AccountLink runtime validation looks good for both SwiftUI-default and forced UIKit-host paths. May 14 SampleApp work added explicit UIKit-host vs SwiftUI-host validation paths. May 20 status: sessions 004 and 005 validated SwiftUI-host load, dismissal, and delegate cleanup for HybridBrokerageAccountOpening and accountlink, but HybridYouthAccountOpening needs complete dismissal coverage. Remaining gaps include AO deep-link coverage, launch wrappers, common-launch, HybridBloomAccountOpening, and explicit UIKit-host mode. Plan to open a draft PR today while validation continues.
|
|
|
|
## Backlog / Future Reference
|
|
|
|
- `PDIAP-11962` - Closure of secret scanning alerts
|
|
Detail: `project-knowledge/02-work-items/pdiap-11962.md`
|
|
Current note: prior closure was submitted on October 9, 2025 and Matthew closed earlier alerts/story on March 5, 2026. Two Google API Key alerts remain open and appear tied to old April 18, 2025 work, not the current REST story.
|
|
|
|
- `PDIAP-11961` - Remediation of Exposed Secrets in XFlow iOS SDK - Request for Rotation/Invalidation
|
|
Detail: `project-knowledge/02-work-items/pdiap-11961.md`
|
|
Current note: related unassigned story for remaining Google API Key alerts; not a current priority but should be preserved for future planning.
|
|
|
|
- `PDIAP-11562` - Investigate if XFlow is being built as debug
|
|
Detail: `project-knowledge/02-work-items/pdiap-11562.md`
|
|
Current note: likely tied to the `XFlowSDK_Debug` variable check in the XFlow podspec and Fid4 consumption, not Sparta-team work; historical Slack suggests Jenkins may build the xcframework path while local development consumes XFlow as a normal library, but this needs current validation.
|
|
|
|
- `PDIAP-12226`, `PDIAP-12227`, `PDIAP-12228` - Sparta backlog items
|
|
Details: `project-knowledge/02-work-items/pdiap-12226.md`, `project-knowledge/02-work-items/pdiap-12227.md`, `project-knowledge/02-work-items/pdiap-12228.md`
|
|
Current note: Slack history ties these to the SpartaSDK follow-up split from initialization/JSON decoding, grid rendering/core components, and interactive/lifecycle behavior. Decoding and rendering are partially complete; interactive components remain blocked by unresolved mobile JavaScript execution.
|
|
|
|
## Recently Completed
|
|
|
|
- `PDIAP-16167` - AccountLink - XFlow causing web view rewrites investigation
|
|
Detail: `project-knowledge/02-work-items/pdiap-16167.md`
|
|
Current note: moved to Done after publishing the Confluence report and sending the findings to Zachary / Jira / Discourse. Future references should frame this as a consumer-side SwiftUI presentation-topology issue, not an XFlow/XFlowViewMaker regression.
|