[Due for payment 2026-06-30] [Due for payment 2026-06-18] [Due for payment 2026-06-17] [$250] Report fields - Initial value page opens with no list value after refreshing the page

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.4.2-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #91627
Email or phone of affected tester (no customers): jsodinjosdjsoinjsiojs@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace settings > Reports.
3. Enable Report fields and upgrade workspace if needed.
4. Click Add field.
5. Click Type and select List.
6. Click List values and add a list value.
7. Click RHP back button.
8. Click Initial value.
9. Refresh the page.

Expected Result:

App will return to Add field page.

Actual Result:

App opens Initial value page with no list value after refreshing the page.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

Bug7176410_1781054397440.5.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7176410

Issue Owner

Current Issue Owner: @ShridharGoel

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022064687816675380929
• Upwork Job ID: 2064687816675380929
• Last Price Increase: 2026-06-10

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/54d4952ff63d00ade7a98e2a12aec9b6dded0f45d52e2e6318a912b873c3f70b

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #91627

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Proposal

Regression from #91627 (migrated InitialListValueSelectorModal from an in-page <Modal> to the deeplinkable dynamic route initial-list-value). Before that PR, the Initial value selector was a modal — not a route — so refreshing simply closed it and dropped you back on the Add field page (the reported "Expected Result"). Now it is a real route, so refresh re-mounts it, and the list values vanish.

What is the root cause of that problem?

The dynamic route WORKSPACE_REPORT_FIELDS_INITIAL_LIST_VALUE declares its entry screen as REPORT_FIELDS_CREATE (ROUTES.ts:824-827).

On refresh, the deeplink rebuilds the stack with CreateReportFieldsPage mounted underneath. That page resets the draft form on every mount (CreateReportFieldsPage.tsx:161-163), and setInitialCreateReportFieldsForm does a full Onyx.set of the draft to {INITIAL_VALUE: ''} (ReportField.ts:104-108) — wiping LIST_VALUES and DISABLED_LIST_VALUES.

The Initial value page then reads formDraft?.[INPUT_IDS.LIST_VALUES] ?? [] (DynamicReportFieldsInitialListValuePage.tsx:69), which is now empty → "Initial value page opens with no list value."

This also means the create flow's transient draft state can never be meaningfully restored on a fresh deeplink/refresh — the data only ever lives in the in-progress draft.

What changes do you think we should make in order to solve the problem?

Two viable paths:

1. Fastest deploy-blocker resolution — revert Migrate InitialListValueSelectorModal to dynamic @react-navigation route #91627. It is a self-contained migration and the regression is inherent to making this transient create-flow step deeplinkable.
2. Forward fix — make the dynamic Initial value page redirect back to the Create page when the draft has no list values (i.e. it was reached via deeplink/refresh rather than the in-app flow). This reproduces the pre-PR "return to Add field page" behavior instead of showing an empty picker.

Why the empty state happens (evidence chain)

• Add list value → written to WORKSPACE_REPORT_FIELDS_FORM_DRAFT.listValues.
• Tap Initial value → Navigation.navigate(createDynamicRoute(...initial-list-value)).
• Refresh → deeplink to .../initial-list-value; entry screen REPORT_FIELDS_CREATE mounts beneath.
• CreateReportFieldsPage mount effect → setInitialCreateReportFieldsForm() → Onyx.set(draft, {INITIAL_VALUE: ''}) overwrites the whole draft, dropping listValues.
• Initial value page renders listValues={formDraft?.[INPUT_IDS.LIST_VALUES] ?? []} → empty.

Note: even if the reset-on-mount were guarded, a truly fresh deeplink (new session) would still have no draft, so option 2's redirect is the behavior that matches user expectation.

Confidence: High — root cause is backed by file:line evidence and explains both reported symptoms (empty list + not returning to Add field page).

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/93138) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[ShridharGoel]

@MelvinBot Implement this and also include the fix for #93141 in the same pull request