Skip to content

[Due for payment 2025-04-23] [HIGH] Receipt View Displays "Hmm it's not here" Message #59348

Closed

Description

@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:
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:

  1. Navigate to the Reports page.
  2. Scroll down to find an expense that has a receipt.
  3. 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?

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

Screenshots/Videos

Add any screenshot/video evidence

(Logs, Onyx state and video for the bug is in OP)

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021907126109137362580
  • Upwork Job ID: 1907126109137362580
  • Last Price Increase: 2025-04-08
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @strepanier03

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Mar 31, 2025
  2. melvin-bot commented on Mar 31, 2025

    @melvin-bot

    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.

  3. MelvinBot commented on Mar 31, 2025

    @MelvinBot
    Contributor

    This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

  4. hungvu193 commented on Mar 31, 2025

    @hungvu193
    Contributor
    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

  5. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 31, 2025
  6. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    on Mar 31, 2025
  7. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed on Apr 1, 2025
  8. 55 remaining items

  9. melvin-bot commented on Apr 16, 2025

    @melvin-bot

    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:

    • @hungvu193 requires payment through NewDot Manual Requests
  10. melvin-bot commented on Apr 16, 2025

    @melvin-bot

    @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]

  11. mvtglobally commented on Apr 19, 2025

    @mvtglobally

    Issue not reproducible during KI retests. (Second week)

  12. melvin-bot commented on Apr 23, 2025

    @melvin-bot

    Payment Summary

    Upwork Job

    BugZero Checklist (@strepanier03)

    • I have verified the correct assignees and roles are listed above and updated the necessary manual offers
    • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants/1907126109137362580/hired)
    • I have paid out the Upwork contracts or cancelled the ones that are incorrect
    • I have verified the payment summary above is correct
  13. removed
    Help WantedApply this label when an issue is open to proposals by contributors
    retest-weeklyApply this label if you want this issue tested on a Weekly basis by Applause
    on Apr 23, 2025
  14. strepanier03 commented on Apr 23, 2025

    @strepanier03
    Contributor

    @hungvu193 - Once you post the checklist I can finish the payment summary and we can close this out. I'll check again later today.

  15. hungvu193 commented on Apr 24, 2025

    @hungvu193
    Contributor

    BugZero Checklist:

    • [Contributor] Classify the bug:
    Bug classification

    Source of bug:

    • 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)
    • 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
    • 3d. QA
    • 3z. Other:
    • [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:

    • Your account has the old reports, ideally reports since 2022.

    Test:

    1. Go to Reports.
    2. Scroll down to the bottom a few times.
    3. Click on any report.
    4. Verify that you can view the report without seeing NotFoundView.

    Do we agree 👍 or 👎

  16. strepanier03 commented on Apr 24, 2025

    @strepanier03
    Contributor

    Payment summary

  17. strepanier03 commented on Apr 24, 2025

    @strepanier03
    Contributor

    @hungvu193 payment summary above, feel free to request. I'm closing this now, thanks again!

  18. garrettmknight commented on May 2, 2025

    @garrettmknight
    Contributor

    $250 approved for @hungvu193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2ExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions