[RCA #72034] Reports - "Action:approve" still applied on search input after "Approvals" are disabled

[vincdargento]

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.61-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: #72034
Email or phone of affected tester (no customers): ibellicotest+2090@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has one workspace created.
Prerequisite 2: Delayed submissions and approvals enabled.

1. Open the Expensify app.
2. Navigate to "Reports"
3. Note that you land on "Approve" section by default.
4. Navigate to "Workspaces" and open workspace menu.
5. Tap on "Workflows"
6. Disable approvals.
7. Navigate to "Reports" again.
8. Note that "action: approve" is still applied on search input.
9. Tap on the menu icon.
10. Note that no section is displayed highlighted or with a checkmark.

Expected Result:

When navigating to "Reports" after approvals are disabled, user should land on "Submit" section, and "Action: approve" shouldn´t be still applied on search input.

Actual Result:

When navigating to "Reports" after approvals are disabled, "Action: approve" is still applied on search input, and when opening menu, no section is highlighted or displayed as opened.

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

bug.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @zanyrenney (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]

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

[melvin-bot]

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

[melvin-bot]

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