Repository navigation
[RCA #64131] Expensify card - RHP back button on "Reconciliation account" does not directly go back to "Card reconciliation" #67638
Description
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.88-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/2148171/test-runs/TR-318/folder/12015321/39317909/816206023?sort=%2Bidentifier
Email or phone of affected tester (no customers): applausetester+310701kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings
Action Performed:
Precondition:
- Workspace is set up with Expensify card feature.
- Workspace is connected to QBO.
- Go to staging.new.expensify.com with applause.expensifail.com account
- Go to workspace settings > Accounting.
- Click Card reconciliation.
- Enable Continuous Reconciliation.
- Click Reconciliation account.
- Click Expensify card settlement account link.
- Click Reconciliation account link.
- Click RHP back button on Reconciliation account page.
Expected Result:
App will directly return to Card reconciliation page (production behavior).
Actual Result:
App goes back to Settlement account page. Another click on RHP back button goes back to Reconciliation account. Third click on RHP back button finally returns to Card reconciliation page.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon Aug 1, 2025
Triggered auto assignment to @muttmuure (
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.melvin-bot commentedon Aug 1, 2025
Triggered auto assignment to @techievivek (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 1, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Aug 1, 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:
[-]RHP back button on "Reconciliation account" does not directly go back to "Card reconciliation"[/-][+]Expensify card - RHP back button on "Reconciliation account" does not directly go back to "Card reconciliation"[/+]grgia commentedon Aug 1, 2025
prob #64131
[-]Expensify card - RHP back button on "Reconciliation account" does not directly go back to "Card reconciliation"[/-][+][RCA #64131] Expensify card - RHP back button on "Reconciliation account" does not directly go back to "Card reconciliation"[/+]7 remaining items
ZhenjaHorbach commentedon Aug 4, 2025
Actually yes
Is this really a regression?
I suppose that after pressing the back button we want to return to the previous screen
And not jump across few screens
So as for me the behavior in test cases is a little incorrect
@techievivek @grgia
What do you think ?
But in any case, we have already opened a PR
So if needed we will fix it immediately after confirmation
techievivek commentedon Aug 5, 2025
@grgia Assigned you as the engineer since you have the required context here.
grgia commentedon Aug 8, 2025
yes we shouldn't jump around screens in the described manner @ZhenjaHorbach
ZhenjaHorbach commentedon Aug 8, 2025
Thanks for your opinion !
So In this case I think we need to update test cases and close this issue after that !
CC: @jponikarchuk
m-natarajan commentedon Aug 13, 2025
@ZhenjaHorbach This is an exploratory issue based on this test case. There’s no step for verifying the back button, so in my view, updating the test case isn’t necessary. Correct me if I’m wrong. I’ve attached the TC steps for your reference.
ZhenjaHorbach commentedon Aug 14, 2025
I think so !
We can leave everything as is !
It's just that after the latest changes the behavior has changed a bit and it has become more consistent
melvin-bot commentedon Aug 21, 2025
@grgia, @muttmuure, @ZhenjaHorbach Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Aug 25, 2025
@grgia, @muttmuure, @ZhenjaHorbach 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Aug 27, 2025
@grgia, @muttmuure, @ZhenjaHorbach 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
ZhenjaHorbach commentedon Aug 28, 2025
@grgia @muttmuure
Let's close this issue