Distance - Receipt briefly shows placeholder after receipt is generated

[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-56-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
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+kh2310002@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to workspace chat
3. Submit a manual expense (if there is no other expense)
4. Go offline
5. Submit a distance expense
6. Go to transaction thread
7. Click Distance
8. Go online
9. Wait for the receipt in the background to generate completely
10. Click outside the RHP to dismiss it

Expected Result:

There will be no changes to the distance receipt and report header

Actual Result:

The distance receipt shows placeholder thumbnil and header changes to "0.00 for Pending..." briefly

Workaround:

Unknown

Platforms:

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

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6651123_1730377599506.20241031_202002.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[lanitochka17]

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

[NikkiWines]

This isn't really breaking enough functionality to be considered a deploy blocker but it should be fixed.

[NikkiWines]

However, most likely coming from #51519 cc: @Gonals @ikevin127 @wildan-m

[ikevin127]

Indeed, this is not a blocker and we discussed it in the PR (#51519 (comment)) and we decided to ship it like this because the fix for it was out of scope for the issue.

Therefore even though this is technically a regression of our PR, we decided not to count it as regression when it comes to compensation.

[NikkiWines]

Ok, marking this as a new issue then

[melvin-bot]

Triggered auto assignment to @sakluger (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.

[wildan-m]

@NikkiWines The issue is likely internal and should be addressed in the backend to resolve discrepancies between transactionBackup and transaction data during online updates. Please refer to this link for an initial investigation into the missing fields. #48630 (comment).

[sakluger]

This falls under #quality since the PR it stems from (#51519 (comment)) was also under #quality.

I'll mark as internal for now and raise a discussion in Slack around prioritization.