IOU - Blank page when opening the detail page of IOU request

[kbecciv]

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

---

Action Performed:

1. Open the testing link staging.new.expensify.com
2. Open any chat where IOU request has been sent
3. Tap on the IOU request to open detail page
4. Repeat the steps and open a detail page of a newly created IOU request

Expected Result:

Detail page to load correctly showing the details of IOU requests

Actual Result:

Blank page / empty section with no details shown

Workaround:

Unknown

Platforms:

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

• Android / native
• Android / Chrome
• iOS / native
• iOS / Safari
• MacOS / Chrome / Safari
• MacOS / Desktop

Version Number: 1.3.14.4

Reproducible in staging?: Yes

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

Notes/Photos/Videos: Any additional supporting documentation

Bug6056372_Scr2.mp4

Expensify/Expensify Issue URL:

Issue reported by: Applause - Internal Team

Slack conversation:

View all open jobs on GitHub

[OSBotify]

👋 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 @johnmlee101 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

[rushatgabhane]

I doubt this is a deploy blocker. It could be because the tester's account isn't on threads beta.

I'm getting code 403 for OpenReport command.

[luacmartins]

This is expected for now. We are creating the thread but are not using the correct header to display the transaction data yet.

[yuwenmemon]

@luacmartins same here - should we just close this out?

[luacmartins]

Yea, we can close this one out and add TestRail cases once the feature is ready.