[HOLD for payment 2024-03-11] [HOLD for payment 2024-03-07] IOU details page appears after delay and it is empty when request is created offline

[m-natarajan]

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: 1.4.45-0
Reproducible in staging?: y
Reproducible in production?: no
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:

Action Performed:

1. Go to staging.new.expensify.com
2. Request money from any user.
3. In 1:1 DM, click on the IOU preview twice to go to transaction thread.
4. Return to IOU report.
5. Click on the IOU preview to go transaction thread again.
6. Note that the details show up after some delay.
7. Go offline.
8. Create another IOU with the same user.
9. Click on the IOU preview twice to go to transaction thread.

Expected Result:

In Step 5, the IOU details page will appear without delay (production behavior).
In Step 9, the IOU details will show even when the request is created offline (production behavior).

Actual Result:

In Step 5, the IOU details page appears after some delay.
In Step 9, the IOU details page is blank when the request is created offline.

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

Bug6396511_1709174884370.20240229_104158.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @sakluger (Bug), see https://stackoverflow.com/c/expensify/questions/14418 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.

[melvin-bot]

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

[m-natarajan]

@techievivek FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.

[techievivek]

Seems like a regression from some recent change and indeed a bad one.

[youssef-lr]

This seems to be coming from here, reverting it fixed it for me. cc @tgolen. Really odd though, I can't see how those changes are causing this, but I double checked and triple checked, reverting the PR definitely fixed it.

Screen.Recording.2024-02-29.at.10.15.10.mov