Chat - Unable to scroll down group confirm page and member details page

[mitarachim]

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.3.54-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: #85229
Email or phone of affected tester (no customers): jsdjosidjiojisojio3@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: Chat Report View

Action Performed:

1. Launch Expensify app in landscape mode.
2. Tap FAB > Start chat.
3. Tap Add to group on any user > Next.
4. Scroll down the confirm page.
   BUG 1: Group confirm page cannot be scrolled down.
5. Tap Start group.
6. Tap on the chat header > Members.
7. Tap on the invited member.
8. Scroll down the page.
   BUG 2: Member details page cannot be scrolled down.

Expected Result:

BUG 1: Group confirm page can be scrolled down.
BUG 2: Member details page can be scrolled down.

Actual Result:

BUG 1: Group confirm page cannot be scrolled down.
BUG 2: Member details page cannot be scrolled down.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7124264_1775609141989.09.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @truph01

[melvin-bot]

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

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