[HOLD for Payment 2024-08-22][$250] Multi tag - Selection mode remains on main tag list after returning from sub tag list

[izarutskaya]

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.0.15-4
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team

Action Performed:

Precondition:

• Workspace is connected to QBO.

1. Launch New Expensify app.
2. Go to workspace settings > Tags.
3. Tap on any main tag.
4. Long press on any sub tag.
5. Tap Select.
6. Swipe right to return to previous page (not app back button).

Expected Result:

Selection mode will be dismissed on the main tag list because main tag cannot be selected for multi tags.

Actual Result:

Selection mode remains on main tag list after returning from sub tag list.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Native
• Android: mWeb Chrome
• iOS: Native
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6559036_1722505630936.ScreenRecording_08-01-2024_17-40-50_1.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~013892471bd59b7984
• Upwork Job ID: 1819070503401243549
• Last Price Increase: 2024-08-01

Issue Owner

Current Issue Owner: @ishpaul777

[melvin-bot]

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

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

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

[izarutskaya]

We think this issue might be related to the #collect project.

[carlosmiceli]

I think the issue comes from here: #46096

@jasperhuangg is this a deploy blocker? Because what I'm seeing is that it's all new functionality, right? Wanna decide what we do here?