Skip to content

Distance - Receipt on confirm page is not clickable #72954

Closed

Description

@mitarachim

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.2.34-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #70975
Email or phone of affected tester (no customers): sdosdisoiudsdjnoisd@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account has self DM.
  1. Go to staging.new.expensify.com
  2. Go to self DM.
  3. Click + > Create expense > Manual.
  4. Enter amount > Next.
  5. On confirm page, add a receipt.
  6. Click on the receipt.
    → Receipt opens with 3-dot menu to replace or download the receipt.
  7. Close the receipt and close the RHP.
  8. Click + > Track distance > Manual.
  9. Enter amount > Next.
  10. On confirm page, add a receipt.
  11. Click on the receipt.

Expected Result:

The receipt on confirm page should be clickable so user can replace or download the receipt (like manual expense).

Actual Result:

The receipt on confirm page is not clickable.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6979681_1760953344729.1.mp4

View all open jobs on GitHub

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Oct 20, 2025
  2. melvin-bot commented on Oct 20, 2025

    @melvin-bot

    Triggered auto assignment to @JmillsExpensify (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. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Oct 20, 2025
  4. melvin-bot commented on Oct 20, 2025

    @melvin-bot

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

  5. melvin-bot commented on Oct 20, 2025

    @melvin-bot

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

  6. github-actions commented on Oct 20, 2025

    @github-actions
    Contributor

    👋 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.
  7. daledah commented on Oct 20, 2025

    @daledah
    Contributor

    It's a new feature appears after my PR - I'll open a follow up soon!

  8. neil-marcellini commented on Oct 20, 2025

    @neil-marcellini
    Contributor

    Not a backend issue.

  9. blimpich commented on Oct 20, 2025

    @blimpich
    Contributor

    reverting here: #73028

  10. blimpich commented on Oct 20, 2025

    @blimpich
    Contributor
  11. IuliiaHerets commented on Oct 20, 2025

    @IuliiaHerets

    @blimpich issue is not repro anymore

    Screen.Recording.2025-10-21.at.03.32.23.1.mp4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions