[$250] The subtitle of QR code is wrong on some pages

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

Action Performed:

1. Open App
2. Go to any report where submitted via delay submissions message is present
3. Click on thread on that message
4. Click on Report header > Share
5. Observe that the QR subtitle is wrong

Expected Result:

It should be shown as submitted via delay submissions (same as report name)

Actual Result:

It is shown as submitted via delay submissions

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

Screenshots/Videos

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022026385957171588249
• Upwork Job ID: 2026385957171588249
• Last Price Increase: 2026-02-24

Issue Owner

Current Issue Owner: @parasharrajat

[melvin-bot]

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

[MelvinBot]

Proposal

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

When viewing the QR code share page for a report that was "submitted via delay submissions", the subtitle displays raw HTML markup (submitted via <a href="...">delay submissions</a>) instead of the plain text "submitted via delay submissions". The same problem affects other automatically-actioned reports (auto-approved, auto-forwarded, auto-paid).

What is the root cause of that problem?

The function computeReportNameBasedOnReportAction in src/libs/ReportNameUtils.ts returns translation strings that contain HTML anchor tags without stripping the HTML first. Specifically, five return statements pass raw HTML through:

1. translate('iou.automaticallySubmitted') at line ~396
2. translate('iou.automaticallyForwarded') at line ~404
3. translate('iou.automaticallyPaidWithBusinessBankAccount') at line ~594
4. translate('iou.automaticallyPaidWithExpensify') at line ~600
5. translate('iou.automaticallyApproved') at line ~610

These translation strings contain <a href="...">...</a> tags (e.g., en.ts:1280: submitted via <a href="${CONST.SELECT_WORKFLOWS_HELP_URL}">delay submissions</a>).

Other return values in the same function already correctly strip HTML using Parser.htmlToText() (e.g., lines ~424, ~458, ~462, ~561, ~628), but these five were missed.

When ShareCodePage.tsx:106 calls getReportName() → computeReportNameBasedOnReportAction(), the raw HTML string flows into the QRShare component's <Text> element (QRShare/index.tsx:92), which renders it as literal text including the markup.

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

Wrap the five affected return statements in computeReportNameBasedOnReportAction (src/libs/ReportNameUtils.ts) with Parser.htmlToText(), following the established pattern already used elsewhere in the same function:

• return translate('iou.automaticallySubmitted') → return Parser.htmlToText(translate('iou.automaticallySubmitted'))
• return translate('iou.automaticallyForwarded') → return Parser.htmlToText(translate('iou.automaticallyForwarded'))
• return translate('iou.automaticallyPaidWithBusinessBankAccount', ...) → return Parser.htmlToText(translate('iou.automaticallyPaidWithBusinessBankAccount', ...))
• return translate('iou.automaticallyPaidWithExpensify') → return Parser.htmlToText(translate('iou.automaticallyPaidWithExpensify'))
• return translate('iou.automaticallyApproved') → return Parser.htmlToText(translate('iou.automaticallyApproved'))

This is safe because components that intentionally render the HTML version (like PureReportActionItem and ContextMenuActions) call translate() directly — they do not go through computeReportNameBasedOnReportAction.

What alternative solutions did you explore? (Optional)

An alternative would be to strip HTML at the consumer level (e.g., wrapping getReportName() in Parser.htmlToText() in ShareCodePage.tsx). However, fixing it at the source in computeReportNameBasedOnReportAction is better because: (a) it follows the existing pattern in the same function, (b) the function's purpose is to return a plain-text report name — not HTML, and (c) it prevents the same bug from appearing in any other consumer of getReportName().

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, or @MelvinBot <your feedback> to refine this analysis.

[melvin-bot]

Current assignee @shubham1206agra is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

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

[PiyushChandra17]

Hi @shubham1206agra step: 2 isn't clear to me, what do you mean when you say: Go to any report where submitted via delay submissions message is present > How can i repro this?

Also i think this is a parsing issue here

App/src/pages/ShareCodePage.tsx

Lines 85 to 101 in 6dae56c

	const subtitle = useMemo(() => {
	if (isReport) {
	if (isExpenseReport(report)) {
	return getPolicyName({report});
	}
	if (isMoneyRequestReport(report)) {
	// generate subtitle from participants
	return getParticipantsAccountIDsForDisplay(report, true)
	.map((accountID) => getDisplayNameForParticipant({accountID, formatPhoneNumber}))
	.join(' & ');
	}
	return getParentNavigationSubtitle(report, isParentReportArchived).workspaceName ?? getChatRoomSubtitle(report, false, isReportArchived);
	}
	return currentUserPersonalDetails.login;
	}, [report, currentUserPersonalDetails.login, isReport, isReportArchived, isParentReportArchived, formatPhoneNumber]);

[shubham1206agra]

Melvin is actually correct, but it caught only 5 out of 9.