Android - Company card - Selection mode persists after changing card feed

[applause-bot]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.4.46-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: #94678
Email or phone of affected tester (no customers): sdsjodijnsdojsosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Workspace Settings

Action Performed:

Precondition:

• Workspace has two direct feed with cards.

1. Launch Expensify app.
2. Go to workspace settings > Company cards.
3. Long tap on any card > Select.
4. Open feed selector.
5. Select another feed.

Expected Result:

Selection mode will exit. Checkbox will not appear on the card.

Actual Result:

Selection mode persists after changing card feed. Checkbox is shown on the card.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome Safari

Screenshots/Videos

To be added by Applause Leads

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7221301

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/56bebdabadcb459c68146488b27d09e54ba0060cf5fd34b0af1575481105307e

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #94678

[melvin-bot]

@JS00001 @ChavdaSachin you have been assigned to this deploy blocker because you reviewed the offending PR: #94678

[melvin-bot]

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

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