Skip to content

[Due for payment 2025-09-04] Reports - Expenses disappear when returning to "Reports" using device´s back button. #69097

Closed

Description

@jponikarchuk

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.1.98-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://test-management.browserstack.com/projects/2219752/test-runs/TR-417/folder/13176922/41237503/856397330
Email or phone of affected tester (no customers): ibellicotest+1646@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb) - Windows 11 / Chrome
App Component: Search

Action Performed:

  1. Open the staging.new.expensify.com website.
  2. Log in with a new account
  3. Create a Workspace and an expense in WS chat
  4. Navigate to "Reports"
  5. Note that expenses preview are correctly displayed.
  6. Navigate to "Inbox" again.
  7. Return to "Reports" using device´s back button.
  8. Note that expense preview are not visible now. Only section header is visible and an empty background is displayed instead of expenses reports.

Expected Result:

Expenses list should remain visible after returning to "Reports" section using device´s back button.

Actual Result:

Empty background is displayed instead of expenses reports when returning to "Reports" section using device´s back button. Expenses disappear and only section header is still visible.

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

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @clarajones-expensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 23, 2025
  2. melvin-bot commented on Aug 23, 2025

    @melvin-bot

    Triggered auto assignment to @clarajones-expensify (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. melvin-bot commented on Aug 23, 2025

    @melvin-bot

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

  4. melvin-bot commented on Aug 23, 2025

    @melvin-bot

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

  5. github-actions commented on Aug 23, 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.
  6. marcaaron commented on Aug 25, 2025

    @marcaaron
    Contributor

    Confirmed the cause is #63623 cc @luacmartins @nkdengineer

  7. 15 remaining items

  8. clarajones-expensify commented on Sep 4, 2025

    @clarajones-expensify
    Contributor

    Hi @luacmartins ! Checking here - does anyone need to be paid for this issue? It seems not and I am good to close this out? Let me know, thanks so much

  9. melvin-bot commented on Sep 4, 2025

    @melvin-bot

    Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.

  10. clarajones-expensify commented on Sep 4, 2025

    @clarajones-expensify
    Contributor

    Think we are good to close this out.

  11. dukenv0307 commented on Sep 22, 2025

    @dukenv0307
    Contributor

    @luacmartins @clarajones-expensify Can you please reopen this issue and process the payment for me since I'm the reviewer of #69204

  12. clarajones-expensify commented on Sep 22, 2025

    @clarajones-expensify
    Contributor

    @luacmartins - what should the payment amount be on this one?

  13. luacmartins commented on Sep 22, 2025

    @luacmartins
    Contributor

    $250 for the PR review

  14. clarajones-expensify commented on Sep 22, 2025

    @clarajones-expensify
    Contributor

    Payment Summary

    Contributor+: @dukenv0307 due $250 via NewDot

  15. quinthar commented on Oct 12, 2025

    @quinthar
    Contributor

    Approved $250 to @dukenv0307

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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions