[HOLD for payment 2024-04-15] [$500] IOU - Opening IOU receipt leads to not here page

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

---

Version Number: 1.4.59-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team

Action Performed:

1. Go to staging.new.expensify.com
2. Go to FAB > Request money.
3. Create a manual request with receipt from user that has no unsettled IOU.
4. In 1:1 DM, click on the IOU preview.
5. Click on the receipt.

Expected Result:

Receipt opens without issue.

Actual Result:

Opening IOU receipt leads to not here page

Workaround:

n/a

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

Bug6435480_1712058058413.receipt.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~0170155bec83d697ff
• Upwork Job ID: 1775191991451828224
• Last Price Increase: 2024-04-02

[melvin-bot]

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

[kbecciv]

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

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

[bernhardoj]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Opening the money request receipt shows not found page.

What is the root cause of that problem?

The condition to show the not found page is checking whether the report parentReportID is not the same as the transaction reportID.

App/src/pages/TransactionReceiptPage.tsx

Line 62 in a1801c8

shouldShowNotFoundPage={(report?.parentReportID ?? '') !== transaction?.reportID}

When this code is made, we can only open the receipt from the transaction thread, so report parentReportID will point to the IOU/expense report, which is the same as transaction reportID.

However, after the one transaction report view PR, we are showing the receipt and other money request fields in the IOU report, so the condition is always false because IOU report parentReportID points to the chat report.

What changes do you think we should make in order to solve the problem?

We should check whether the report is a money request report or not. If it's a money request report, we just take the reportID, otherwise take the parentReportID.

const moneyRequestReportID = ReportUtils.isMoneyRequestReport(report) ? report?.reportID : report?.parentReportID;

shouldShowNotFoundPage={(moneyRequestReportID ?? '') !== transaction?.reportID}

[shubham1206agra]

@bernhardoj Can you update your solution to cover Track Expense on selfDM?

[bernhardoj]

I don't see the problem with track expense

[shubham1206agra]

Just make a track expense with the receipt. And try to open the receipt.

[bernhardoj]

Screen.Recording.2024-04-02.at.23.40.39.mov

Works fine.

[shubham1206agra]

Oh. Looks like a BE issue, then. Please continue here.

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

[melvin-bot]

Triggered auto assignment to @alexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

[bernhardoj]

PR is ready

[NikkiWines]

confirmed this works on staging as expected now 👍

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[alexpensify]

@dukenv0307 can we confirm if this blocker notice is valid or an error? Thanks!

[dukenv0307]

@alexpensify this is not valid the context here #39512 (comment)

[alexpensify]

Perfect, thank you for the update!

[alexpensify]

Update: We are waiting for this one to go into production

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix opening receipt page from IOU report leads to not found page #39419

If no regressions arise, payment will be issued on 2024-04-15. 🎊

For reference, here are some details about the assignees on this issue:

• @bernhardoj requires payment (Needs manual offer from BZ)
• @dukenv0307 requires payment (Needs manual offer from BZ)

[melvin-bot]

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@dukenv0307] The PR that introduced the bug has been identified. Link to the PR:
• [@dukenv0307] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
• [@dukenv0307] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
• [@dukenv0307] Determine if we should create a regression test for this bug.
• [@dukenv0307] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
• [@alexpensify] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

[alexpensify]

@dukenv0307 and @bernhardoj - please submit a request here:

https://www.upwork.com/jobs/~0170155bec83d697ff

On Monday, I can complete the payment process. Thanks!

[bernhardoj]

Applied!

[dukenv0307]

@dukenv0307 and @bernhardoj - please submit a request here:

@alexpensify Thanks, I've applied to the job too

[melvin-bot]

Payment Summary

Upwork Job

• ROLE: @bernhardoj paid $(500) via Upwork (LINK)
• ROLE: @dukenv0307 paid $(500) via Upwork (LINK)

BugZero Checklist (@alexpensify)

• I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
• I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1775191991451828224/hired)
• I have paid out the Upwork contracts or cancelled the ones that are incorrect
• I have verified the payment summary above is correct

[alexpensify]

@dukenv0307 and @bernhardoj - I've sent you offers via Upwork. Please accept and I can complete the payment process.

[bernhardoj]

@alexpensify accepted

[alexpensify]

Thanks, I was able to complete the payment to @bernhardoj.

@dukenv0307, please accept the offer in Upwork, and I can complete the process. Thanks!

[dukenv0307]

@alexpensify I accepted the UW offer

[alexpensify]

Perfect, @dukenv0307 has been paid via Upwork. Closing since everyone has been paid via Upwork.