[HOLD for payment 2025-01-22] [HOLD for payment 2025-01-21] Track expense - Receipt does not load after sharing expense with accountant

[IuliiaHerets]

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.84-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5441811 Email or phone of affected tester (no customers): sdjomisodsmsdo@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.0 / Chrome App Component: Other

Action Performed:

1. Go to staging.new.expensify.com
2. Log in with a new Gmail account.
3. Select "Track and budget expenses" during onboarding.
4. Complete the onboarding.
5. Go to self DM.
6. Track an expense without receipt.
7. Click Share it with my accountant.
8. Click on the receipt placeholder.
9. Add any receipt.
10. Submit the expense to the workspace.
11. Go to transaction thread.
12. Click on the receipt.

Expected Result:

Receipt will load without issue.

Actual Result:

Receipt shows green placeholder in the preview. When the receipt is viewed in full screen, it shows an attachment icon.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

https://github.com/user-attachments/assets/3a0bdcea-b428-4c19-9fac-ef0a36330b6c

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @OfstadC

[melvin-bot[bot]]

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

[melvin-bot[bot]]

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

[melvin-bot[bot]]

💬 A slack conversation has been started in #expensify-open-source

[github-actions[bot]]

:wave: 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.

[Pujan92]

@CyberAndrii seems to be from our PR, plz check on it.

[CyberAndrii]

PR is ready. Should I wait for @Pujan92 to be assigned here before marking it as ready for review?

[Pujan92]

You can mark it as ready for review, I will review it.

[rlinoz]

Asked for a retest after CP https://expensify.slack.com/archives/C9YU7BX5M/p1736776525661989

[kavimuru]

Issue fixed

https://github.com/user-attachments/assets/0f6af3ed-f780-4a8f-b72b-6b0916e6b9fa

[melvin-bot[bot]]

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

[melvin-bot[bot]]

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

• https://github.com/Expensify/App/pull/55126

If no regressions arise, payment will be issued on 2025-01-21. :confetti_ball:

[melvin-bot[bot]]

@rlinoz @OfstadC @rlinoz The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot[bot]]

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

• https://github.com/Expensify/App/pull/55126

If no regressions arise, payment will be issued on 2025-01-22. :confetti_ball:

[melvin-bot[bot]]

@rlinoz @OfstadC @rlinoz The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[rlinoz]

BugZero Checklist:

• [x] [Contributor] Classify the bug:

Bug classification

Source of bug:

• [x] 1a. Result of the original design (eg. a case wasn't considered)
• [ ] 1b. Mistake during implementation
• [ ] 1c. Backend bug
• [ ] 1z. Other:

Where bug was reported:

• [ ] 2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
• [x] 2b. Reported on staging (eg. found during regression or PR testing)
• [ ] 2d. Reported on a PR
• [ ] 2z. Other:

Who reported the bug:

• [ ] 3a. Expensify user
• [ ] 3b. Expensify employee
• [ ] 3c. Contributor
• [x] 3d. QA
• [ ] 3z. Other:

• [x] [Contributor] 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: N/A reverted by authors of the original PR

• [ ] [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source 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:

• [ ] [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.