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-09-04] Reports - After returning to report via browser back button, report does not show pagination #69066
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:
Go to staging.new.expensify.com
Create a workspace
Create two reports via FAB > Create report
Go to Reports > Reports
Open any report
→ The report view shows the pagination with arrows
Open search router
Type anything and hit Enter
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 evidenceBug6924184_1755888696342.missing_pagination.mp4
👋 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:
Identify the pull request that introduced this issue and revert it.
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
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?
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
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:
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.
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.
Activity
melvin-bot commentedon Aug 22, 2025
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.github-actions commentedon Aug 22, 2025
👋 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:
melvin-bot commentedon Aug 22, 2025
Triggered auto assignment to @AndrewGable (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 22, 2025
💬 A slack conversation has been started in #expensify-open-source
[-]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[/+]sumo-slonik commentedon Aug 25, 2025
I’m already looking into it and I’ll try to fix it as soon as possible.
21 remaining items
mountiny commentedon Aug 28, 2025
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?
mountiny commentedon Aug 28, 2025
I feel like this is:
cc @JmillsExpensify @trjExpensify for your thoughts
JmillsExpensify commentedon Aug 28, 2025
I agree with that. I think we should plan to address it, though let's not block on it.
sumo-slonik commentedon Aug 29, 2025
In the issue it was written to do this only for search reports:
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.
JmillsExpensify commentedon Aug 29, 2025
Agreed, let's handle it separately.
mountiny commentedon Aug 29, 2025
Yep sorry for that, lets handle that separately
melvin-bot commentedon Sep 4, 2025
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.
CortneyOfstad commentedon Sep 5, 2025
Is there a separate GH that has been created @mountiny? If so, is this good to close?
mountiny commentedon Sep 8, 2025
I think we can clsoe this one as it should be handled in the new PR