You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2025-04-23] [HIGH] Receipt View Displays "Hmm it's not here" Message #59348
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: 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:@quinthar Slack conversation (hyperlinked to channel name): #Quality
Action Performed:
Navigate to the Reports page.
Scroll down to find an expense that has a receipt.
Click on the receipt to view it.
Expected Result:
The receipt should open and display properly.
Actual Result:
Initially, the receipt page displayed a "Hmm" message.
After closing and reopening the receipt, it displayed correctly without console errors.
The URL generated for the receipt view appears excessively long.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.28-15-staging and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@hungvu193@strepanier03@hungvu193 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]
[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: N/A
[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.
Regression Test Proposal
Precondition:
Your account has the old reports, ideally reports since 2022.
Test:
Go to Reports.
Scroll down to the bottom a few times.
Click on any report.
Verify that you can view the report without seeing NotFoundView.
Activity
melvin-bot commentedon Mar 31, 2025
Triggered auto assignment to @strepanier03 (
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.MelvinBot commentedon Mar 31, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
hungvu193 commentedon Mar 31, 2025
trim.7CE4A52E-BE6D-4DD6-A480-08F8565769E3.MOV
I can reproduce this one consistently based on the OP steps.
Can you assign me to this issue? @strepanier03
Slack post: https://expensify.enterprise.slack.com/archives/C02NK2DQWUX/p1743425028932909
55 remaining items
melvin-bot commentedon Apr 16, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.28-15-staging and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2025-04-23. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Apr 16, 2025
@hungvu193 @strepanier03 @hungvu193 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]
mvtglobally commentedon Apr 19, 2025
Issue not reproducible during KI retests. (Second week)
melvin-bot commentedon Apr 23, 2025
Payment Summary
Upwork Job
BugZero Checklist (@strepanier03)
strepanier03 commentedon Apr 23, 2025
@hungvu193 - Once you post the checklist I can finish the payment summary and we can close this out. I'll check again later today.
hungvu193 commentedon Apr 24, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[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: https://github.com/Expensify/App/pull/48940/files#r2057354606
[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: N/A
[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.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
strepanier03 commentedon Apr 24, 2025
Payment summary
strepanier03 commentedon Apr 24, 2025
@hungvu193 payment summary above, feel free to request. I'm closing this now, thanks again!
garrettmknight commentedon May 2, 2025
$250 approved for @hungvu193