[$250] Not here page shown when started a chat offline and starting it again online

[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.2.9-0
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #67525
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: MacBook Air 15.6.1 Chrome, iPhone 15 iOS 18.5 Safari
App Component: Chat Report View

Action Performed:

1. Sign in to ND
2. Go offline
3. Create a group chat with two other users you you never chatted before
4. Split expense in the group
5. Go online
6. Click on FAB - Start chat, enter an email of one of the users from step 3, press Enter

Expected Result:

User is navigated to the chat with the other user, the split expense is displayed in the chat

Actual Result:

"Not here" page is shown, when trying to create a chat with the user you already created a chat offline, when split the expense in group. The issue also occurs, when start a 1:1 chat offline, send a message, then trying to start it again online

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

Bug6941038_1757550232814.Not_here.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~021966171355267205888
• Upwork Job ID: 1966171355267205888
• Last Price Increase: 2025-09-25
• Automatic offers:
• ShridharGoel | Contributor | 108962553

Issue Owner

Current Issue Owner: @bfitzexpensify

[melvin-bot]

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

[melvin-bot]

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

[melvin-bot]

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

[ShridharGoel]

Proposal

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

When a user creates chats while offline (e.g., starts a group chat and splits an expense, or creates a 1:1 chat and sends a message), then goes online and uses FAB → Start chat to start a chat with one of those participants, the app shows the “Hmm... it’s not here” page instead of the actual chat.

What is the root cause of that problem?

Navigation used the initial optimistic report ID captured before server reconciliation and did not re-resolve which report to open after the modal dismissal. If the server responded with preexistingReportID, the optimistic report could be removed or replaced, making the captured ID invalid. The code immediately navigated with the stale report?.reportID and then again in a setTimeout with the same value, triggering the Not Found page.

App/src/libs/actions/Report.ts

Lines 1383 to 1401 in b85094e

	if (shouldDismissModal) {
	Navigation.onModalDismissedOnce(() => {
	Navigation.onModalDismissedOnce(() => {
	if (!report?.reportID) {
	return;
	}
	Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report.reportID));
	});
	});
	Navigation.dismissModal();
	} else if (report?.reportID) {
	Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report.reportID));
	}
	// In some cases when RHP modal gets hidden and then we navigate to report Composer focus breaks, wrapping navigation in setTimeout fixes this
	setTimeout(() => {
	Navigation.isNavigationReady().then(() => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(report?.reportID)));
	}, 0);

This code always navigates using the optimistic report?.reportID captured earlier, even if the server later replaces it (e.g., due to an existing chat between the participants).

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

We now resolve the target report ID at the time of navigation (after modal dismissal and again then), by looking up the latest existing chat via getChatByParticipants([...participantAccountIDs, currentUserAccountID]). If such a chat exists, we navigate to its real reportID; otherwise we fallback to the previously computed report?.reportID. This ensures we don’t navigate to stale optimistic IDs and avoids the Not Found page when the server consolidates to a preexisting chat.

Updated code:

// Helper to resolve the latest chat after potential server reconciliation (e.g., preexistingReportID replacement)
const getLatestTargetReportID = (): string | undefined => {
    // Prefer a freshly resolved existing chat if available
    const latestChat = getChatByParticipants([...participantAccountIDs, currentUserAccountID]);
    return latestChat?.reportID ?? report?.reportID;
};

if (shouldDismissModal) {
    Navigation.onModalDismissedOnce(() => {
        Navigation.onModalDismissedOnce(() => {
            const targetReportID = getLatestTargetReportID();
            if (!targetReportID) {
                return;
            }
            Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(targetReportID));
        });
    });
    Navigation.dismissModal();
} else {
    const targetReportID = getLatestTargetReportID();
    if (targetReportID) {
        Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(targetReportID));
    }
}

setTimeout(() => {
    const targetReportID = getLatestTargetReportID();
    if (!targetReportID) {
        return;
    }
    Navigation.isNavigationReady().then(() => Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(targetReportID)));
}, 0);

This keeps behavior consistent with existing flows while making navigation robust against offline-to-online reconciliation.

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

Add new unit tests for this and similar flows.

[huult]

Hey everyone, is this issue still reproducible?