[Due for payment now] Fix the tappable nested rows on group by results on mobile

[trjExpensify]

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: v9.2.64-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: No
Issue reported by: @trjExpensify
Slack conversation (hyperlinked to channel name): #71448 CC: @Krishna2323 @dubielzyk-expensify

Action Performed:

Pre-requisite: Mobile-only

1. Create a workspace
2. Create two expenses
3. Submit the report
4. Go to Reports > Accounting > Unapproved cash
5. Expand the group

Note: I did steps for unapproved cash, as it seems like the easiest for you to test without bank account/card setup etc.

Expected Result:

• The nested expense rows are tappable
• They have a right caret alongside the expense amount

Actual Result:

The row is not tappable and doesn't have a right caret

Workaround:

Yes, go to Reports > Expenses and find the expense.

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

Screenshots/Videos

In-line above

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @trjExpensify

[melvin-bot]

Current assignee @trjExpensify is eligible for the Bug assigner, not assigning anyone new.

[Krishna2323]

Working on the PR...

[Krishna2323]

@trjExpensify should the whole row be pressable, or do we only need to add a chevron that takes the user to the expense?

[Krishna2323]

@trjExpensify this isn’t a regression from my PR — it behaved the same way even before my changes were merged. I switched to the commit just before my PR and here’s the recording:

I'm available to work on this if we still need this change. Thanks!

Monosnap.screencast.2025-11-27.00-00-05.mp4

[dubielzyk-expensify]

should the whole row be pressable, or do we only need to add a chevron that takes the user to the expense?

My take is that we should use the same tap target as we do on a regular expense. The whole thing is a tap target except the checkbox for multi-select

[trjExpensify]

I'm available to work on this if we still need this change. Thanks!

Waa? So what did impact it? Anyhow, yes, we still need it 👍

My take is that we should use the same tap target as we do on a regular expense. The whole thing is a tap target except the checkbox for multi-select

Agree with Jon. 👍