[Due for payment 2025-09-16] [HOLD on new PR] [$250] [BACK BUTTON] Back Button on Report Detail Page Resets Scroll Position on Reports List

[m-natarajan]

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.84-4
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dannymcclain
Slack conversation (hyperlinked to channel name): #Expensify Bugs

Action Performed:

1. Open the Reports page
2. Scroll down the list and select a report that's not near the top
3. After viewing the report, click the back button in the top-left corner

Expected Result:

The user should be returned to the same scroll position on the Reports page where they were before opening the report.

Actual Result:

The Reports page scrolls all the way to the top, and the user loses their place in the list.

Workaround:

Unknown

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

Platforms Tested:

On which of our officially supported platforms was this issue tested:

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

Screenshots/Videos

Add any screenshot/video evidence

CleanShot.2025-07-18.at.11.09.28.mp4

Recording.1433.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021948728734052183015
• Upwork Job ID: 1948728734052183015
• Last Price Increase: 2025-08-08
• Automatic offers:
• huult | Contributor | 108404009

Issue Owner

Current Issue Owner: @twisterdotcom

[melvin-bot]

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

[thelullabyy]

Proposal

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

The Reports page scrolls all the way to the top, and the user loses their place in the list.

What is the root cause of that problem?

What is the root cause of that problem?

The Search list component is unmounted when navigating away. Upon remounting, it does not restore the previous scroll position because there is no logic in place to preserve or restore the scroll offset.
See https://reactnavigation.org/docs/stack-navigator/#detachinactivescreens

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

1. Add logic to save and get the scroll offset:

    const listRef = useRef<FlashList<SearchListItem>>(null);
    const {saveScrollOffset, getScrollOffset} = useContext(ScrollOffsetContext);
    const route = useRoute();
    const scrollToSavePosition = useCallback(() => {
        const offset = getScrollOffset(route);

        if (!(offset && listRef.current)) {
            return;
        }

        // We need to use requestAnimationFrame to make sure it will scroll properly on iOS.
        requestAnimationFrame(() => {
            if (!(offset && listRef.current)) {
                return;
            }
            listRef.current.scrollToOffset({offset}); // Can use animated here if needed
        });
    }, [getScrollOffset, route]);

    const scrollOffset = getScrollOffset(route);

2. Update onScroll and onLayout function to use the above functions:

App/src/components/Search/SearchList.tsx

Line 439 in bf05168

onScroll={onScroll}

                onScroll={(e) => {
                    saveScrollOffset(route, e.nativeEvent.contentOffset.y);
                    onScroll?.(e);
                }}

App/src/components/Search/SearchList.tsx

Line 447 in bf05168

onLayout={onLayout}

                onLayout={(e)=>{
                    scrollToSavePosition()
                    onLayout?.(e)
                }}

3. Update logic to clear the scroll offset storage:
   

   App/src/components/ScrollOffsetContextProvider.tsx

   Line 84 in bf05168

   if (!scrollOffsetKeysOfExistingScreens.includes(key)) {

            if (!scrollOffsetKeysOfExistingScreens.includes(key) && !(key === `${SCREENS.SEARCH.ROOT}-global`)) {

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)

[melvin-bot]

@twisterdotcom Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@twisterdotcom Eep! 4 days overdue now. Issues have feelings too...

[twisterdotcom]

Wow yes, this is annoying. I thought this was to do with he browser back button which is a whole other kettle of fish, but this seems like something we should solve for sure.

[melvin-bot]

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