[Due for payment 2025-06-11] [$250] Help - In share to expensify page, help page displays "missing help content for route."

[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.46-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: N/a
Email or phone of affected tester (no customers): Applausetester+ivappa@applause.expensif
Issue reported by: Applause Internal Team
Device used: Redminote note 10s android 13
App Component: User Settings

Action Performed:

Pre-condition: Keep logged in app with expensifail account

1. Open a image
2. Tap share and select expensify app
3. Tap help icon

Note: issue happens in Start chat, Create expense page also

Expected Result:

In share to expensify page, help page must not display " missing help content for route."

Actual Result:

In share to expensify page, help page displays " missing help content for route."

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/~021924497682439578424
• Upwork Job ID: 1924497682439578424
• Last Price Increase: 2025-05-19

[melvin-bot]

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

[truph01]

Proposal

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

• In share to expensify page, help page displays " missing help content for route.". It is expected behavior.

What is the root cause of that problem?

• "missing help content for route.": The Help page displays this message because the Share routes (e.g., ShareTab, SubmitTab) are not configured in the help content map:
  https://github.com/Expensify/App/blob/main/src/components/SidePanel/HelpContent/helpContentMap.tsx
  So, I think it is expected behavior.

• More importantly, the displayed message is incomplete. It shows only "Missing help content for route:" without the actual route name. This makes debugging or identifying the missing route difficult. And it is the bug we need to address.

• The reason the route name is missing stems from how the route is derived:
  

  App/src/components/SidePanel/HelpComponents/HelpContent.tsx

  Lines 55 to 66 in 32d67b3

  	const route = useMemo(() => {
  	const path = normalizedConfigs[routeName]?.path;
  	if (!path) {
  	return '';
  	}
  	const cleanedPath = path.replaceAll('?', '');
  	const expenseType = getExpenseType(transaction);
  	const reportOverride = expenseType ? `:${CONST.REPORT.HELP_TYPE.EXPENSE}/:${expenseType}` : `:${getHelpPaneReportType(report)}`;
  	return cleanedPath.replaceAll(':reportID', reportOverride);
  	}, [routeName, transaction, report]);

• When the current routeName is ShareTab, the normalizedConfigs doesn't include any screen named ShareTab due to this logic:
  

  App/src/libs/Navigation/linkingConfig/config.ts

  Lines 1746 to 1753 in 32d67b3

  	[NAVIGATORS.SHARE_MODAL_NAVIGATOR]: {
  	initialRouteName: SCREENS.SHARE.ROOT,
  	screens: {
  	[SCREENS.SHARE.ROOT]: {path: ROUTES.SHARE_ROOT},
  	[SCREENS.SHARE.SHARE_DETAILS]: {path: ROUTES.SHARE_DETAILS.route},
  	[SCREENS.SHARE.SUBMIT_DETAILS]: {path: ROUTES.SHARE_SUBMIT_DETAILS.route},
  	},
  	},

• As a result, the route ends up being an empty string (''), and the message appears incomplete.

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

• We need to update the linking configuration to ensure ShareTab and SubmitTab are included in the navigation config. We should update:
  

  App/src/libs/Navigation/linkingConfig/config.ts

  Lines 1746 to 1753 in 32d67b3

  	[NAVIGATORS.SHARE_MODAL_NAVIGATOR]: {
  	initialRouteName: SCREENS.SHARE.ROOT,
  	screens: {
  	[SCREENS.SHARE.ROOT]: {path: ROUTES.SHARE_ROOT},
  	[SCREENS.SHARE.SHARE_DETAILS]: {path: ROUTES.SHARE_DETAILS.route},
  	[SCREENS.SHARE.SUBMIT_DETAILS]: {path: ROUTES.SHARE_SUBMIT_DETAILS.route},
  	},
  	},

to:

[NAVIGATORS.SHARE_MODAL_NAVIGATOR]: {
    initialRouteName: SCREENS.SHARE.ROOT,
    screens: {
        [SCREENS.SHARE.ROOT]: {
            path: ROUTES.SHARE_ROOT,
            screens: {
                [CONST.TAB.SHARE.SHARE]: {
                    path: ROUTES.SHARE_ROOT_SHARE,
                    exact: true,
                },
                [CONST.TAB.SHARE.SUBMIT]: {
                    path: ROUTES.SHARE_ROOT_SUBMIT,
                    exact: true,
                },
            },
        },
    },
},

• This change requires adding the corresponding route constants:

SHARE_ROOT_SHARE: 'share/root/share',
SHARE_ROOT_SUBMIT: 'share/root/submit',

• This ensures that both ShareTab and SubmitTab are included in the config and their route names can be resolved correctly for help content mapping and diagnostics.

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

• None

What alternative solutions did you explore? (Optional)

[melvin-bot]

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

[melvin-bot]

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