[Due for payment 2025-08-13] [$250] Composer - Edit compose box is not auto-focused when editing a message in report page

[jponikarchuk]

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.1.85-2
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #65229
Email or phone of affected tester (no customers): expensify416+da2@gmail.com
Issue reported by: Applause Internal Team
Device used: Android
App Component: Other

Action Performed:

Precondition: User should have. a workspace

1. Go to Reports
2. Tap FAB > Create Report > Send a message
3. When keyboard is up, long press the message > Tap Edit comment

Expected Result:

Editing Composer should be focused

Actual Result:

Main composer is focused instead of editing composer

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021948409177921856446
• Upwork Job ID: 1948409177921856446
• Last Price Increase: 2025-07-24

Issue Owner

Current Issue Owner: @VictoriaExpensify

[melvin-bot]

Triggered auto assignment to @laurenreidexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[Eskalifer1]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Composer - Edit compose box is not auto-focused when editing a message in report page

What is the root cause of that problem?

The problem is that we use FlatList instead of InvertedFlatList, as in the case of a simple chat. FlatList itself has a removeClippedSubviews prop, which removes an element from the virtual tree to improve optimization.

What changes do you think we should make in order to solve the problem?

Since this prop breaks a certain logic, we pass it as false by default for InvertedFlatList

App/src/components/InvertedFlatList/index.native.tsx

Line 20 in 57f0196

removeClippedSubviews={false}

Similarly, we can pass this prop as false for this component:

App/src/components/MoneyRequestReportView/MoneyRequestReportActionsList.tsx

Lines 636 to 671 in 57f0196

	<FlatList
	initialNumToRender={INITIAL_NUM_TO_RENDER}
	accessibilityLabel={translate('sidebarScreen.listOfChatMessages')}
	testID="money-request-report-actions-list"
	style={styles.overscrollBehaviorContain}
	data={visibleReportActions}
	renderItem={renderItem}
	keyExtractor={keyExtractor}
	onLayout={recordTimeToMeasureItemLayout}
	onEndReached={onEndReached}
	onEndReachedThreshold={0.75}
	onStartReached={onStartReached}
	onStartReachedThreshold={0.75}
	ListHeaderComponent={
	<>
	<MoneyRequestViewReportFields
	report={report}
	policy={policy}
	/>
	<MoneyRequestReportTransactionList
	report={report}
	transactions={transactions}
	newTransactions={newTransactions}
	reportActions={reportActions}
	hasComments={reportHasComments}
	isLoadingInitialReportActions={showReportActionsLoadingState}
	scrollToNewTransaction={scrollToNewTransaction}
	/>
	</>
	}
	keyboardShouldPersistTaps="handled"
	onScroll={trackVerticalScrolling}
	contentContainerStyle={[shouldUseNarrowLayout ? styles.pt4 : styles.pt2]}
	ref={reportScrollManager.ref}
	ListEmptyComponent={!isOffline && showReportActionsLoadingState ? <ReportActionsListLoadingSkeleton /> : undefined} // This skeleton component is only used for loading state, the empty state is handled by SearchMoneyRequestReportEmptyState
	/>

removeClippedSubviews={false}

We can only pass this for Android native, if necessary.

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

N/A

What alternative solutions did you explore? (Optional)

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~021948409177921856446

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @dukenv0307 (External)

[dukenv0307]

@Eskalifer1's proposal looks good to me

🎀👀🎀 C+ reviewed