Skip to content

[Due for payment 2025-09-04] Reports - After returning to report via browser back button, report does not show pagination #69066

Closed

Description

@lanitochka17

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?: Y
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 TestRail: #66608
Email or phone of affected tester (no customers): sdjionsjdoidnosdinj@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create a workspace
  3. Create two reports via FAB > Create report
  4. Go to Reports > Reports
  5. Open any report
    → The report view shows the pagination with arrows
  6. Open search router
  7. Type anything and hit Enter
  8. Click browser back button or device back button

Expected Result:

After returning to report via browser back button, report will show pagination

Actual Result:

After returning to report via browser back button, report does not show pagination

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6924184_1755888696342.missing_pagination.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @CortneyOfstad

Activity

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

    @melvin-bot

    Triggered auto assignment to @CortneyOfstad (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. github-actions commented on Aug 22, 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.
  4. melvin-bot commented on Aug 22, 2025

    @melvin-bot

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

  5. melvin-bot commented on Aug 22, 2025

    @melvin-bot

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

  6. changed the title [-]Reports - After returning to report via browser back button, report does not show nagination[/-] [+]Reports - After returning to report via browser back button, report does not show pagination[/+] on Aug 24, 2025
  7. sumo-slonik commented on Aug 25, 2025

    @sumo-slonik
    Contributor

    I’m already looking into it and I’ll try to fix it as soon as possible.

  8. 21 remaining items

  9. mountiny commented on Aug 28, 2025

    @mountiny
    Contributor

    Sorry was ooo. @sumo-slonik could you clear the onyx search later in the flow so basically it would never be cleared - just changed after new report is selected

    But also why does it rely on a search - shouldnt the arrows be also in Inbox > Expense report?

  10. mountiny commented on Aug 28, 2025

    @mountiny
    Contributor

    I feel like this is:

    • Important flow enough to care about it - we might not block on it now, but if there is no solution now that fits into our system, I do not feel good about our general approach to this - it is not a good UX is the arrows are missing after going back.
    • We should rather make sure the underlying solution supports this flow too

    cc @JmillsExpensify @trjExpensify for your thoughts

  11. JmillsExpensify commented on Aug 28, 2025

    @JmillsExpensify
    Contributor

    I agree with that. I think we should plan to address it, though let's not block on it.

  12. sumo-slonik commented on Aug 29, 2025

    @sumo-slonik
    Contributor

    Sorry was ooo. @sumo-slonik could you clear the onyx search later in the flow so basically it would never be cleared - just changed after new report is selected
    But also why does it rely on a search - shouldnt the arrows be also in Inbox > Expense report?

    In the issue it was written to do this only for search reports:

    Image

    and that’s what I did that way. The key point there was the approach to the approve process with this navigation.
    I think we can rework it so that it also works in the inbox (basically it would just require preparing a list of report IDs to navigate through), but I’d prefer to handle that separately as a follow-up.

  13. JmillsExpensify commented on Aug 29, 2025

    @JmillsExpensify
    Contributor

    Agreed, let's handle it separately.

  14. mountiny commented on Aug 29, 2025

    @mountiny
    Contributor

    Yep sorry for that, lets handle that separately

  15. 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.

  16. CortneyOfstad commented on Sep 5, 2025

    @CortneyOfstad
    Contributor

    Is there a separate GH that has been created @mountiny? If so, is this good to close?

  17. mountiny commented on Sep 8, 2025

    @mountiny
    Contributor

    I think we can clsoe this one as it should be handled in the new PR

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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions