[HOLD for payment 2024-11-20] [$250] Expense-Expense preview is hidden briefly when returning to expense report via header subtitle

[lanitochka17]

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.0.40-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): applausetester+kh230901@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to DM
3. Submit at least two expenses to the user
4. Go to transaction thread of the first expense
5. Click on the header subtitle link to go back to expense report

Expected Result:

The second expense preview will show instantly after returning to expense report via header subtitle (production behavior)

Actual Result:

The second expense preview is hidden briefly after returning to expense report via header subtitle

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6615158_1727291074734.IOU_thread.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021839062492993280361
• Upwork Job ID: 1839062492993280361
• Last Price Increase: 2024-10-30
• Automatic offers:
• huult | Contributor | 104757569

Issue Owner

Current Issue Owner: @RachCHopkins

[melvin-bot]

Triggered auto assignment to @francoisl (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

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

[lanitochka17]

We think that this bug might be related to #wave-collect - Release 1

[francoisl]

I also notice a short delay on production, albeit shorter than on staging. Roughly like 50ms on production, and 200ms on staging.
It doesn't look like there's any API call happening when returning to the parent report, so it's probably not due to anything changing in Onyx.

There's nothing that stands out in the checklist so I'm going to open this up for proposals. Doesn't seem worthy of blocking though.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021839062492993280361