[$250] Expense - Report title gets updated only after opening the report

[jponikarchuk]

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: V9.3.15-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #81428
Email or phone of affected tester (no customers): dreamnitethedragon@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redminote 10S Android 13
App Component: Money Requests

Action Performed:

1. Launch app
2. Create a workspace
3. Open workspace chat
4. Turn on forced offline via 4finger gesture
5. Create a report
6. Go to workspace settings reports and set id as report:id
7. Open workspace chat
8. Create a report
9. Go to reports and set id as report:currency
   10.Open workspace chat
   11.Create a report
   12.Togge off forced offline via 4finger gesture
10. Note report created in step 5 and step 8 not showing currency header
11. Open the report created in step 5 and step 8
12. Note report header for step 5 and step 8 report changes to currency

Expected Result:

Once the app is back online, reports created in steps 5 and 8 should immediately show the updated currency header.

Actual Result:

Reports created while forced offline (steps 5 & 8) do not show the currency header in the reports list even after turning online.

The currency header gets updated only after opening the report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022019817626752717723
• Upwork Job ID: 2019817626752717723
• Last Price Increase: 2026-02-06

Issue Owner

Current Issue Owner: @mananjadhav

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @stephanieelliott (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[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.

[OSBotify]

🔍 Investigation Summary

Classification: Frontend bug
Causing PR: #81428 - "Remove custom report names beta gating" by @neil-marcellini (High confidence)
Related Issues: None found

Recommendation: REVERT

PR #81428 exposed a pre-existing bug in the custom report names implementation. When reports are created offline, the optimistic REPORT_NAME_VALUE_PAIRS data is set but never properly cleared/updated when the API call succeeds, causing report titles to not update until the report is opened.

The fix requires changes to the App codebase to add proper successData/failureData handling for REPORT_NAME_VALUE_PAIRS. Reverting this PR will restore the previous behavior where only beta users were affected.

Labels: No label changes needed - this is a frontend bug blocking the App deploy, so DeployBlockerCash should remain.

📋 Detailed Analysis

Evidence

The issue describes that:

1. Reports are created while forced offline (steps 5, 8, 11)
2. Custom report name formulas are configured (steps 6, 9)
3. When coming back online (step 12), the report names do not automatically update
4. Report names only update after opening each report (steps 14-15)

This behavior started appearing in staging (v9.3.15-1) and is not reproducible in production, which confirms it was introduced by a PR in the current deploy. Melvin-bot correctly identified PR #81428.

Verification

PR #81428 removed the CUSTOM_REPORT_NAMES beta gating, making the custom report name logic run unconditionally. I verified the PR modifies:

• src/libs/ReportUtils.ts - buildOptimisticExpenseReport and buildOptimisticEmptyReport functions
• src/libs/actions/Report/index.ts - Report creation logic
• src/libs/ReportTitleUtils.ts - Removed beta checks from updateTitleFieldToMatchPolicy

Root Cause

In /home/runner/work/App/App/src/libs/actions/Report/index.ts, the function buildNewReportOptimisticData (around line 3000-3228) creates optimistic data for new reports:

1. Line 3136 calls updateTitleFieldToMatchPolicy(reportID, policy) which adds optimistic updates to REPORT_NAME_VALUE_PAIRS
2. However, the successData (line 3183) and failureData (line 3163) arrays do NOT include entries for REPORT_NAME_VALUE_PAIRS
3. The TypeScript types confirm this: optimisticData includes REPORT_NAME_VALUE_PAIRS (line 3090), but successData and failureData only include REPORT | REPORT_ACTIONS (lines 3163, 3183)

When a report is created offline and the API call succeeds later, the optimistic REPORT_NAME_VALUE_PAIRS data persists because there is no successData to clear/update it with the backend response. This causes the report name to remain stale until the report is opened, which triggers a refresh.

Before PR #81428, this bug only affected users in the CUSTOM_REPORT_NAMES beta. After removing the beta check, it now affects all users creating reports with custom name formulas while offline.

[neil-marcellini]

I don't think this needs to be a blocker because it's a very rare edge case, but we should fix it.