[Awaiting Checklist] [Due for payment 2025-09-22] [$250] Android - Reports - Search input and filters disappear after deleting several reports

[nlemma]

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.98-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: #66608
Email or phone of affected tester (no customers): ibellicotest+1648@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 / Android 12 (Hybrid app)
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace available.

1. Open the Expensify app.
2. Create several reports (At least 10) via FAB > Create Report.
3. Navigate to "Reports"
4. Perform a search that return all the reports using "Groupby:Reports"
5. Scroll to the bottom of the results.
6. Open the last report.
7. Tap on "More" and delete the report.
8. When navigated back to results, note that the deleted report can be seen at the bottom, moving up, before disappearing.
9. Repeat steps 6 - 7 with the last report, until page is not scrollable anymore.
10. Note that after deleting several reports, when page is not scrollable anymore, search input and filters on top, disappear.

Expected Result:

Search input and filter options, should remain visible after deleting several reports on the results list, after a search.

Actual Result:

After performing a search, and deleting several reports from the bottom of the results list, search input and filters options, disappear.
Also, everytime a report is deleted, when navigated back to the results list, the deleted report can be briefly seen at the bottom, moving up until disappearing from list.

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

Bug6924562_1755929632977.Input.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021970054831210556932
• Upwork Job ID: 1970054831210556932
• Last Price Increase: 2025-09-22

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

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

[dmkt9]

Proposal

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

After performing a search, and deleting several reports from the bottom of the results list, search input and filters options, disappear.
Also, everytime a report is deleted, when navigated back to the results list, the deleted report can be briefly seen at the bottom, moving up until disappearing from list.

What is the root cause of that problem?

After performing a search, and deleting several reports from the bottom of the results list, search input and filters options, disappear.

• When we delete an item, it reduces contentSize.height and simultaneously triggers the onScroll event. We use the onScroll event to determine whether to show or hide the SearchPageHeader. However, if SearchPageHeader is currently hidden and deleting an item causes windowHeight > contentSize.height, then topBarOffset is not recalculated, resulting in SearchPageHeader remaining hidden:
  

  App/src/pages/Search/SearchPageNarrow.tsx

  Lines 86 to 91 in c46f457

  	onScroll: (event) => {
  	runOnJS(triggerScrollEvent)();
  	const {contentOffset, layoutMeasurement, contentSize} = event;
  	if (windowHeight > contentSize.height) {
  	return;
  	}

Also, everytime a report is deleted, when navigated back to the results list, the deleted report can be briefly seen at the bottom, moving up until disappearing from list.

• The fade-out-up animation was introduced in PR #63623 and is expected behavior:
  

  App/src/components/Search/SearchList/index.tsx

  Line 250 in c46f457

  exiting={shouldAnimate ? FadeOutUp.duration(CONST.SEARCH.EXITING_ANIMATION_DURATION).easing(easing) : undefined}

  
  However, if we don’t want this animation to apply to the last item, we can modify the logic.

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

1. Restore topBarOffset:
   

   App/src/pages/Search/SearchPageNarrow.tsx

   Lines 89 to 91 in c46f457

   	if (windowHeight > contentSize.height) {
   	return;
   	}

if (windowHeight > contentSize.height) {
    topBarOffset.set(StyleUtils.searchHeaderDefaultOffset);
    return;
}

2. Skip animation for the last item:

• Pass the index to renderItem inside renderItemWithKeyboardFocus:
  

  App/src/components/Search/SearchList/BaseSearchList/index.tsx

  Lines 59 to 80 in c46f457

  	const renderItemWithKeyboardFocus = useCallback(
  	({item, index}: {item: SearchListItem; index: number}) => {
  	const isItemFocused = focusedIndex === index;
  	const onFocus = (event: NativeSyntheticEvent<ExtendedTargetedEvent>) => {
  	// Prevent unexpected scrolling on mobile Chrome after the context menu closes by ignoring programmatic focus not triggered by direct user interaction.
  	if (isMobileChrome() && event.nativeEvent) {
  	if (!event.nativeEvent.sourceCapabilities) {
  	return;
  	}
  	// Ignore the focus if it's caused by a touch event on mobile chrome.
  	// For example, a long press will trigger a focus event on mobile chrome
  	if (event.nativeEvent.sourceCapabilities.firesTouchEvents) {
  	return;
  	}
  	}
  	setFocusedIndex(index);
  	};
  	return renderItem(item, isItemFocused, onFocus);
  	},
  	[focusedIndex, renderItem, setFocusedIndex],
  	);

• Then check and apply conditional animation logic here:
  

  App/src/components/Search/SearchList/index.tsx

  Lines 249 to 254 in c46f457

  	<Animated.View
  	exiting={shouldAnimate ? FadeOutUp.duration(CONST.SEARCH.EXITING_ANIMATION_DURATION).easing(easing) : undefined}
  	entering={undefined}
  	style={styles.overflowHidden}
  	layout={shouldAnimate && hasItemsBeingRemoved ? LinearTransition.easing(easing).duration(CONST.SEARCH.EXITING_ANIMATION_DURATION) : undefined}
  	>

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

NA

What alternative solutions did you explore? (Optional)

NA

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.

2025-08-24.23-38-46.mp4

[sumo-slonik]

I’m already looking into it and I’ll try to fix it as soon as possible.

[RachCHopkins]

Thanks @sumo-slonik !