[Due for payment 2025-06-25] [Better Expense Report View] Inconsistency between View and Submit button in expense row while in selection mode

[lanitochka17]

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.63-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): sdjoisdjosdijsod@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

• Have a paid report and unsubmitted report in the workspace chat

1. Launch Expensify app
2. Go to Reports
3. Long tap on any expense row
4. Tap Select
5. Tap Submit button while in selection mode
6. Tap View button while in selection mode

Expected Result:

In selection mode

• Submit button will submit the expense
• View button will open the expense thread

Actual Result:

In selection mode,

• Submit button submits the expense
• View button does not open the expense thread. It unselects/selects the expense row instead

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 evidence

Bug6854740_1749489921915.Screen_Recording_20250610_012215_Expensify.mp4

View all open jobs on GitHub

[melvin-bot]

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

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

[Julesssss]

We just switched to the multi-select UI. I'm going to downgrade from blocker as it's just a new inconsistency. I believe we'll just need to align the behaviour of the row item buttons when we're in the multi select mode. I commented here.

[Julesssss]

I believe we'll just need to align the behaviour of the row item buttons when we're in the multi select mode. I commented #62474 (comment).

@SzymczakJ @rushatgabhane @mountiny , let me know if you disagree with this, thanks!

[shawnborton]

Makes sense to me that it doesn't need to be a blocker.

[mountiny]

@shawnborton Should the button work or the entire row would select/ deselect?

I would say the entire row should act as select/deselect

cc @Expensify/design

[shawnborton]

Do we remember what we were doing before? I could see an argument that while in select mode, there should only be one tap target, and that's just tapping the whole row to select/unselect as you are saying. I would be fine with that approach.

Curious what the other design homies think too!