[Due for payment 2026-04-30] [Due for payment 2026-04-28] iOS-Self DM-App not scroll down after created the new expense in self DM

[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: v9.3.60-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-19604/folder/13176877/41237351/1336303953
Email or phone of affected tester (no customers): lekima20+65404@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: iPhone 16 pro/ 26.3.1
App Component: Money Requests

Action Performed:

1. Open app
2. Navigate to self DM chat
3. Create an expense
4. Create the second expense

Expected Result:

App should scroll down to the second expense

Actual Result:

After created the second expense, app still displays at the first expense

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7131281_1776334965233.Mhzt0108_1_.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @situchan

[melvin-bot]

Triggered auto assignment to @lakchote (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.

[OSBotify]

Investigation Summary. Classification: Frontend bug. Causing PR: #85114 - Migrate main chat to FlashList with inverted flag - by @VickyStash (High confidence). Recommendation: REVERT. PR 85114 replaces InvertedFlatList with InvertedFlashList in ReportActionsList.tsx. The iOS-only auto-scroll regression (chat not scrolling to newly created second expense) is consistent with the inverted FlashList behavior change introduced by this PR. Assigned: @VickyStash (PR author), @situchan @Julesssss @mountiny (approving reviewers). Labels: DeployBlockerCash kept (frontend App PR caused the issue). DeployBlocker removed since this is a frontend-only change with no backend involvement. Evidence: PR 85114 was merged on 2026-04-15 and is confirmed in the StagingDeployCash deploy checklist for v9.3.60-1. The issue is iOS-only and staging-only, matching a freshly introduced regression. The PR replaces InvertedFlatList with InvertedFlashList in src/pages/inbox/report/ReportActionsList.tsx, fundamentally changing how the chat list renders and handles scroll position. Verification: Affected file src/pages/inbox/report/ReportActionsList.tsx is directly modified by PR 85114. The auto-scroll behavior upon new expense creation is governed by useScrollToEndOnNewMessageReceived, which calls reportScrollManager.scrollToBottom. PR 85114 also changed the shouldScrollToEndAfterLayout reset logic from an immediate state update to a debounced timeout. Root Cause: The migration from InvertedFlatList to InvertedFlashList changed how the inverted list handles scroll position tracking on iOS. The scroll-to-bottom trigger path may be suppressed by the new debounced shouldScrollToEndAfterLayout logic or by differences in how FlashList tracks scroll offsets on iOS. The bug being iOS-only aligns with the separate iOS vs Android code paths in FlashList (the PR added a distinct Android MVCP patch but iOS relies on native scroll behavior).