[Due for payment 2026-06-17] [$250] Learn more link is unresponsive in import transactions RHP

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.

---

Version Number: 9.3.99-0
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: @mukhrr
Slack conversation (hyperlinked to channel name): #Open Source

Action Performed:

1. Navigate to wallet
   2. Click import transactions
2. Fill form -> Next
3. Choose any file
4. Click "Learn more" link

Expected Result:

Link opens related help dot link

Actual Result:

Nothing happens on click link

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

REC-20260603205132.mp4

Recording.2952.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022062504897804600335
• Upwork Job ID: 2062504897804600335
• Last Price Increase: 2026-06-04

Issue Owner

Current Issue Owner: @mallenexpensify

[MelvinBot]

Proposal

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

The "Learn more" link on the import-transactions column-mapping screen (Wallet → Import transactions → fill form → Next → choose a file) is unresponsive. Clicking it does nothing instead of opening the related help article.

What is the root cause of that problem?

The column-mapping screen renders ImportSpreadsheetColumns, whose "Learn more" link is <TextLink href={learnMoreLink ?? ''}>. When learnMoreLink is not provided, the href falls back to an empty string, so the click resolves to openLink(''), which opens nothing.

TransactionsImportedPage renders ImportSpreadsheetColumns without passing a learnMoreLink prop. Every other caller passes one, so only the Wallet import-transactions flow has a dead link.

Evidence: all other callers pass learnMoreLink, this one does not

ImportedMembersPage.tsx        learnMoreLink={CONST.IMPORT_SPREADSHEET.MEMBERS_ARTICLE_LINK}
CompanyCardsImportedPage.tsx   learnMoreLink={CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL}
ImportedTagsPage.tsx           learnMoreLink={CONST.IMPORT_SPREADSHEET.TAGS_ARTICLE_LINK}
ImportedMultiLevelTagsPage.tsx learnMoreLink={CONST.IMPORT_SPREADSHEET.MULTI_LEVEL_TAGS_ARTICLE_LINK}
ImportedPerDiemPage.tsx        learnMoreLink={CONST.IMPORT_SPREADSHEET.CATEGORIES_ARTICLE_LINK}
ImportedCategoriesPage.tsx     learnMoreLink={CONST.IMPORT_SPREADSHEET.CATEGORIES_ARTICLE_LINK}
TransactionsImportedPage.tsx   (none) -> href="" -> dead link

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

Pass a learnMoreLink to ImportSpreadsheetColumns in TransactionsImportedPage.tsx:150, pointing at the personal-card import help article:

<ImportSpreadsheetColumns
    spreadsheetColumns={spreadsheetColumns}
    columnNames={columnNames}
    importFunction={importTransactions}
    errors={isValidationEnabled ? validate() : undefined}
    columnRoles={columnRoles}
    isButtonLoading={isImporting}
    learnMoreLink={CONST.IMPORT_SPREADSHEET.IMPORT_TRANSACTIONS_ARTICLE_LINK}
/>

Add the new constant to CONST.IMPORT_SPREADSHEET:

IMPORT_TRANSACTIONS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet',

(The matching help article already exists at docs/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md.)

What alternative solutions did you explore?

Alternatively, harden ImportSpreadsheetColumns so it only renders the "Learn more" TextLink when learnMoreLink is a non-empty string. This guards against any future caller forgetting the prop, but the Wallet flow should still get a real article link, so the primary fix above is preferred (the two can also be combined).

---

Next Steps for Contributor+ team:
To accept: @MelvinBot implement [this](https://github.com/Expensify/App/issues/92665) to create a draft PR.
To refine: @MelvinBot <your feedback>
To reject: Explain why you are rejecting Melvin's proposal.

[MobileMage]

Proposal

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

After navigating Wallet → Import transactions, filling the form, tapping Next, and selecting a spreadsheet file, the user lands on the column-mapping screen (TransactionsImportedPage) which shows a "Learn more" link next to the import description. Clicking the link does nothing — no new tab opens, no navigation occurs. The link renders with the standard link style so it looks interactive, but the click is silently swallowed on Chrome and Safari.

What is the root cause of that problem?

The bug is a missing prop on the <ImportSpreadsheetColumns> instance rendered inside TransactionsImportedPage. The shared ImportSpreadsheetColumns component renders the "Learn more" affordance via <TextLink href={learnMoreLink ?? ''}>, falling back to an empty string when the parent doesn't provide a URL:

App/src/components/ImportSpreadsheetColumns.tsx

Lines 73 to 79 in df574e0

	<Text>
	{customHeaderText ?? (
	<>
	{translate('spreadsheet.importDescription')}
	<TextLink href={learnMoreLink ?? ''}>{` ${translate('common.learnMore')}`}</TextLink>.
	</>
	)}

TransactionsImportedPage is the only consumer of this component that omits learnMoreLink — categories, members, tags, multi-level tags, per diem, and company-cards imports all pass a CONST.IMPORT_SPREADSHEET.*_ARTICLE_LINK (or COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL), but the wallet flow forgets it:

App/src/pages/settings/Wallet/TransactionsImportedPage.tsx

Lines 150 to 157 in df574e0

	<ImportSpreadsheetColumns
	spreadsheetColumns={spreadsheetColumns}
	columnNames={columnNames}
	importFunction={importTransactions}
	errors={isValidationEnabled ? validate() : undefined}
	columnRoles={columnRoles}
	isButtonLoading={isImporting}
	/>

The chain that turns the missing prop into a silent no-op is precise. Clicking the link triggers TextLink.openLinkOnTap → openLinkUtil('', environmentURL) in src/libs/actions/Link.ts. Inside openLink, every branch falls through with an empty href: hasSameExpensifyOrigin('', ...) throws on new URL('') and returns false, getInternalNewExpensifyPath('') early-returns '' at line 150, and the same for getInternalExpensifyPath. So execution reaches openExternalLink(href) at line 232 with href === '', which calls asyncOpenURL(Promise.resolve(), '', ...). The web implementation of asyncOpenURL then short-circuits on the first line:

const asyncOpenURL: AsyncOpenURL = (promise, url, ...) => {
    if (!url) {
        return;
    }

That guard (in src/libs/asyncOpenURL/index.web.ts lines 12-15) is exactly why nothing happens on click — the empty string is falsy and the function bails before ever calling Linking.openURL. So this is not a TextLink/PressableWithoutFeedback rendering issue, not an HTML-<a> failure, and not a Text ancestor problem; the click handler fires correctly, but the URL passed downstream is empty, and the URL opener intentionally no-ops on empty input.

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

Pass an appropriate help-article URL as the learnMoreLink prop in TransactionsImportedPage. The closest existing constant is CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL (https://help.expensify.com/articles/new-expensify/connect-credit-cards/Company-Card-Settings), which the parallel "Add a company card via CSV" flow already uses for the same "map columns from CSV" screen in CompanyCardsImportedPage at line 188. Since wallet import-transactions also produces a CSV-fed card (it calls importTransactionsFromCSV which creates a personal card), the same article applies and reuses an already-shipped constant rather than introducing a new one that would need design/help-team sign-off. The change is one line in TransactionsImportedPage.tsx:

<ImportSpreadsheetColumns
    spreadsheetColumns={spreadsheetColumns}
    columnNames={columnNames}
    importFunction={importTransactions}
    errors={isValidationEnabled ? validate() : undefined}
    columnRoles={columnRoles}
    isButtonLoading={isImporting}
    learnMoreLink={CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL}
/>

This is safe — no other caller is affected, and ImportSpreadsheetColumns already handles a populated learnMoreLink correctly (it's the documented prop on the component). If the help team prefers a dedicated wallet article, the fix is the same shape but swaps in a new CONST.IMPORT_SPREADSHEET.IMPORT_TRANSACTIONS_ARTICLE_LINK constant added beside the existing CATEGORIES_ARTICLE_LINK / MEMBERS_ARTICLE_LINK entries in src/CONST/index.ts; the call site change in TransactionsImportedPage is identical.

What alternative solutions did you explore? (Optional)

Hardening ImportSpreadsheetColumns to hide the "Learn more" link when learnMoreLink is falsy (wrapping the <TextLink> in {learnMoreLink && ...}) was considered as a defensive fallback so future consumers can't reproduce the same bug. It was rejected as the primary fix because the reporter and existing UX clearly intend the link to be present and functional; removing it would silently degrade the screen instead of fixing it. The guard would be a fine follow-up alongside the call-site fix.

[kamronbek04]

Proposal

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

In the wallet Import transactions flow, after choosing a file you land on the column-mapping screen whose intro text ends in a "Learn more" link. Clicking that link does nothing — it never opens the help article. Reproducible on all platforms in staging and production.

What is the root cause of that problem?

The "Learn more" link lives in the shared ImportSpreadsheetColumns component. Its href is driven entirely by the learnMoreLink prop:

https://github.com/Expensify/App/blob/main/src/components/ImportSpreadsheetColumns.tsx#L73-L80

{translate('spreadsheet.importDescription')}
<TextLink href={learnMoreLink ?? ''}>{` ${translate('common.learnMore')}`}</TextLink>.

When learnMoreLink is not supplied, the ?? '' fallback renders the link with an empty href. TextLink still renders and is clickable, but on press it calls openLink('', environmentURL) (TextLink.tsx#L41-L46 → Link.openLink). With an empty string none of the internal/external path branches match and there is no URL to open, so the click is a silent no-op — exactly the "nothing happens" symptom.

The reason learnMoreLink is empty here specifically: the transactions screen never passes it. TransactionsImportedPage mounts ImportSpreadsheetColumns without a learnMoreLink:

https://github.com/Expensify/App/blob/main/src/pages/settings/Wallet/TransactionsImportedPage.tsx#L141-L148

Every other consumer of this component does pass one — ImportedTagsPage (TAGS_ARTICLE_LINK), ImportedMultiLevelTagsPage (MULTI_LEVEL_TAGS_ARTICLE_LINK), ImportedMembersPage (MEMBERS_ARTICLE_LINK), ImportedPerDiemPage (CATEGORIES_ARTICLE_LINK). The transactions page was the one that shipped without wiring a link, and there's no TRANSACTIONS_ARTICLE_LINK defined in CONST.IMPORT_SPREADSHEET to wire to (CONST/index.ts#L8546-L8554). So this is a longstanding latent gap, not a regression — the link has been dead since the wallet import flow was added.

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

Two-part fix: define the missing help-article constant, then pass it on the transactions screen.

Add the constant alongside the existing import links in CONST.IMPORT_SPREADSHEET:

         CATEGORIES_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Create-categories#import-custom-categories',
         MEMBERS_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Invite-members-and-assign-roles#import-a-group-of-members',
         TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags',
         MULTI_LEVEL_TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags#import-multi-level-tags-from-a-spreadsheet',
+        TRANSACTIONS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/wallet-and-cards/Import-transactions-from-a-spreadsheet',
     },

Then pass it in TransactionsImportedPage (CONST is already imported there at line 17):

             <ImportSpreadsheetColumns
                 spreadsheetColumns={spreadsheetColumns}
                 columnNames={columnNames}
                 importFunction={importTransactions}
                 errors={isValidationEnabled ? validate() : undefined}
                 columnRoles={columnRoles}
                 isButtonLoading={isImporting}
+                learnMoreLink={CONST.IMPORT_SPREADSHEET.TRANSACTIONS_ARTICLE_LINK}
             />

The exact helpdot slug above should be confirmed against the canonical article for importing wallet transactions (the C+ / assignee can supply the final URL); the structural fix — defining the constant and threading it through — is what makes the link live.

I'd pair this with a small hardening of ImportSpreadsheetColumns so the component never renders a clickable-but-dead link again. Instead of falling back to an empty href, only render the link when a URL exists:

-                                {translate('spreadsheet.importDescription')}
-                                <TextLink href={learnMoreLink ?? ''}>{` ${translate('common.learnMore')}`}</TextLink>.
+                                {translate('spreadsheet.importDescription')}
+                                {!!learnMoreLink && (
+                                    <>
+                                        <TextLink href={learnMoreLink}>{` ${translate('common.learnMore')}`}</TextLink>.
+                                    </>
+                                )}

This guard is the safety net; the real win for this issue is supplying the link. Scope boundary: this touches only the transactions import screen and the shared component's empty-href handling — the other four import flows already pass valid links and render identically, so they're unaffected. No action/Onyx logic changes.

Verification: Wallet → Import transactions → fill form → Next → choose a CSV → on the column-mapping screen, click "Learn more". It should open the import-transactions help article (in a new tab on web). With the component guard, any future consumer that forgets learnMoreLink will show the description text with no dangling link instead of a dead one.

What alternative solutions did you explore? (Optional)

I considered fixing this only in ImportSpreadsheetColumns by hiding the link when learnMoreLink is empty, without adding the constant. Rejected: that would permanently strip the "Learn more" affordance from the transactions flow — the issue's expected behavior is that the link opens the article, not that it disappears. Hiding it trades a dead link for a missing feature. The article link is the actual missing piece, so it has to be supplied; the visibility guard is worth keeping only as defensive hardening on top, not as the fix.

[KJ21-ENG]

Proposal

What is the root cause of that problem?

The wallet import-transactions mapping screen uses the shared ImportSpreadsheetColumns header, which renders the "Learn more" link from the optional learnMoreLink prop.

TransactionsImportedPage does not pass that prop, so the shared component renders the link with an empty href. When the user clicks it, TextLink has no HelpDot URL to open, so the link appears unresponsive.

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

Pass a real HelpDot URL into ImportSpreadsheetColumns from src/pages/settings/Wallet/TransactionsImportedPage.tsx.

The narrowest fix is to reuse the existing file-feed help URL already used by the analogous workspace company-card CSV import mapping screen: CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL. If product wants a wallet-specific article instead, add a dedicated constant and pass that from this wallet page.

Keep this scoped to the wallet transaction-import mapping page. Do not change global TextLink or openLink behavior, and do not change the other spreadsheet import callers because they already pass valid contextual links.

Add focused coverage for TransactionsImportedPage so the mapping screen passes the expected learnMoreLink to ImportSpreadsheetColumns or opens that URL when the "Learn more" link is pressed.

What alternative solutions did you explore? (Optional)

I considered adding a default URL inside ImportSpreadsheetColumns, but the component is shared by categories, members, tags, per diem, company cards, and wallet transactions. A global default could send unrelated import flows to the wrong article, so the wallet caller should provide its own destination.

[melvin-bot]

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

[melvin-bot]

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

[oqildev]

Proposal

What is the root cause of that problem?

The "Learn more" link on the import column-mapping screen is rendered by ImportSpreadsheetColumns, and its href comes from an optional learnMoreLink prop that falls back to an empty string:

App/src/components/ImportSpreadsheetColumns.tsx

Lines 76 to 77 in c07f8e4

	{translate('spreadsheet.importDescription')}
	<TextLink href={learnMoreLink ?? ''}>{` ${translate('common.learnMore')}`}</TextLink>.

The wallet flow's screen — TransactionsImportedPage — mounts ImportSpreadsheetColumns but never passes learnMoreLink:

App/src/pages/settings/Wallet/TransactionsImportedPage.tsx

Lines 141 to 148 in c07f8e4

	<ImportSpreadsheetColumns
	spreadsheetColumns={spreadsheetColumns}
	columnNames={columnNames}
	importFunction={importTransactions}
	errors={isValidationEnabled ? validate() : undefined}
	columnRoles={columnRoles}
	isButtonLoading={isImporting}
	/>

So learnMoreLink is undefined, href resolves to '', and clicking does nothing. TextLink calls openLink(href, environmentURL); with an empty string there's no internal NewDot/OldDot path to match, so it falls through to openExternalLink(''), which opens nothing:

App/src/components/TextLink.tsx

Lines 42 to 48 in c07f8e4

	const openLink = (event: GestureResponderEvent | KeyboardEvent) => {
	if (onPress) {
	onPress(event);
	} else {
	openLinkUtil(href, environmentURL);
	}
	};

This is specific to the wallet import-transactions flow. Every other caller of ImportSpreadsheetColumns passes a real link, which is why their "Learn more" works — e.g. categories:

App/src/pages/workspace/categories/ImportedCategoriesPage.tsx

Lines 154 to 157 in c07f8e4

	columnRoles={columnRoles}
	isButtonLoading={isImportingCategories}
	learnMoreLink={CONST.IMPORT_SPREADSHEET.CATEGORIES_ARTICLE_LINK}
	/>

(members, tags, multi-level tags, per diem, and company cards all do the same). TransactionsImportedPage is the one screen that was missed.

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

This is a render/props gap plus one missing config constant — no logic change needed.

1. There's no transactions-specific article constant yet; the IMPORT_SPREADSHEET block only has categories/members/tags links:

   App/src/CONST/index.ts

   Lines 8489 to 8497 in c07f8e4

   	IMPORT_SPREADSHEET: {
   	ICON_WIDTH: 180,
   	ICON_HEIGHT: 160,
   	CATEGORIES_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Create-categories#import-custom-categories',
   	MEMBERS_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Invite-members-and-assign-roles#import-a-group-of-members',
   	TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags',
   	MULTI_LEVEL_TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags#import-multi-level-tags-from-a-spreadsheet',
   	},

   Add one — e.g. TRANSACTIONS_ARTICLE_LINK — pointing at the existing HelpDot article for this exact feature: https://help.expensify.com/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet (the doc lives at docs/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md).

2. Pass it through in TransactionsImportedPage by adding learnMoreLink={CONST.IMPORT_SPREADSHEET.TRANSACTIONS_ARTICLE_LINK} to the ImportSpreadsheetColumns usage at TransactionsImportedPage.tsx#L141-L148, matching how every other importer wires it up.

No offline/optimistic/error-path concerns here — it's a static help link.

What alternative solutions did you explore? (Optional)

Harden ImportSpreadsheetColumns so it can never render a dead link — only render the <TextLink> when learnMoreLink is truthy (and drop the trailing . accordingly) at ImportSpreadsheetColumns.tsx#L76-L77. I'd treat this as a complementary guard, not the fix: the design clearly wants a "Learn more" link on this screen, so hiding it would leave the wallet flow as the only importer without help text. It's worth doing on top of the real fix to stop future callers from shipping the same empty-href regression, but on its own it just trades a dead link for a missing one.

Hardcode the URL inline in the component rather than threading a prop — rejected because the component is shared across six+ flows that each need a different article, so per-caller learnMoreLink is the right seam.

[Abdulloh0109]

Proposal

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

On the import-transactions column-mapping screen (Wallet → Import transactions → fill form → Next → choose a file), the "Learn more" link is dead — clicking it does nothing instead of opening the related help article. Reproduces on web/desktop (Windows Chrome, macOS Chrome/Safari).

What is the root cause of that problem?

The link has no URL behind it, and the URL opener intentionally no-ops on an empty string. Here is the full chain at the reported version.

TransactionsImportedPage renders ImportSpreadsheetColumns but never passes a learnMoreLink prop:

App/src/pages/settings/Wallet/TransactionsImportedPage.tsx

Lines 150 to 157 in df574e0

	<ImportSpreadsheetColumns
	spreadsheetColumns={spreadsheetColumns}
	columnNames={columnNames}
	importFunction={importTransactions}
	errors={isValidationEnabled ? validate() : undefined}
	columnRoles={columnRoles}
	isButtonLoading={isImporting}
	/>

Inside the shared component, the "Learn more" affordance falls back to an empty string when the prop is missing — href={learnMoreLink ?? ''}:

App/src/components/ImportSpreadsheetColumns.tsx

Lines 73 to 79 in df574e0

	<Text>
	{customHeaderText ?? (
	<>
	{translate('spreadsheet.importDescription')}
	<TextLink href={learnMoreLink ?? ''}>{` ${translate('common.learnMore')}`}</TextLink>.
	</>
	)}

Clicking it runs TextLink's handler, which calls openLinkUtil(href, environmentURL) with href === '':

App/src/components/TextLink.tsx

Lines 41 to 46 in df574e0

	const openLink = (event: GestureResponderEvent | KeyboardEvent) => {
	if (onPress) {
	onPress(event);
	} else {
	openLinkUtil(href, environmentURL);
	}

In openLink, every branch is skipped for an empty href: hasSameExpensifyOrigin('', …) is false, getInternalNewExpensifyPath('') and getInternalExpensifyPath('') resolve to nothing, so execution falls through to openExternalLink(href) with an empty string:

App/src/libs/actions/Link.ts

Lines 174 to 232 in df574e0

	function openLink(href: string, environmentURL: string, isAttachment = false) {
	const hasSameOrigin = Url.hasSameExpensifyOrigin(href, environmentURL);
	const hasExpensifyOrigin = Url.hasSameExpensifyOrigin(href, CONFIG.EXPENSIFY.EXPENSIFY_URL) || Url.hasSameExpensifyOrigin(href, CONFIG.EXPENSIFY.STAGING_API_ROOT);
	const internalNewExpensifyPath = getInternalNewExpensifyPath(href);
	const internalExpensifyPath = getInternalExpensifyPath(href);
	const isNarrowLayout = getIsNarrowLayout();
	const currentState = navigationRef.getRootState();
	const isRHPOpen = currentState?.routes?.at(-1)?.name === NAVIGATORS.RIGHT_MODAL_NAVIGATOR;
	let shouldCloseRHP = false;
	if (!isNarrowLayout && isRHPOpen) {
	const targetWillNavigateToRHP = willRouteNavigateToRHP(internalNewExpensifyPath as Route);
	if (!targetWillNavigateToRHP) {
	shouldCloseRHP = true;
	} else if (hasSameOrigin) {
	// Cross-tab RHP→RHP: swap the background tab in place so the RHP stays mounted and the
	// user sees only the RHP content update + the underlying tab animate, no close+reopen
	// flicker (issue: https://github.com/Expensify/App/issues/89710).
	swapBackgroundTabForRHPTarget(currentState, internalNewExpensifyPath as Route);
	}
	}
	// There can be messages from Concierge with links to specific NewDot reports. Those URLs look like this:
	// https://www.expensify.com.dev/newdotreport?reportID=3429600449838908 and they have a target="_blank" attribute. This is so that when a user is on OldDot,
	// clicking on the link will open the chat in NewDot. However, when a user is in NewDot and clicks on the concierge link, the link needs to be handled differently.
	// Normally, the link would be sent to Link.openOldDotLink() and opened in a new tab, and that's jarring to the user. Since the intention is to link to a specific NewDot chat,
	// the reportID is extracted from the URL and then opened as an internal link, taking the user straight to the chat in the same tab.
	if (hasExpensifyOrigin && href.indexOf('newdotreport?reportID=') > -1) {
	const reportID = href.split('newdotreport?reportID=').pop();
	const reportRoute = ROUTES.REPORT_WITH_ID.getRoute(reportID);
	if (shouldCloseRHP) {
	Navigation.closeRHPFlow();
	}
	Navigation.navigate(reportRoute);
	return;
	}
	// If we are handling a New Expensify link then we will assume this should be opened by the app internally. This ensures that the links are opened internally via react-navigation
	// instead of in a new tab or with a page refresh (which is the default behavior of an anchor tag)
	if (internalNewExpensifyPath && hasSameOrigin) {
	if (isAnonymousUser() && !canAnonymousUserAccessRoute(internalNewExpensifyPath)) {
	signOutAndRedirectToSignIn();
	return;
	}
	if (shouldCloseRHP) {
	Navigation.closeRHPFlow();
	}
	Navigation.navigate(internalNewExpensifyPath as Route);
	return;
	}
	// If we are handling an old dot Expensify link we need to open it with openOldDotLink() so we can navigate to it with the user already logged in.
	// As attachments also use expensify.com we don't want it working the same as links.
	const isPublicOldDotURL = (Object.values(CONST.OLD_DOT_PUBLIC_URLS) as string[]).includes(href);
	if (internalExpensifyPath && !isAttachment && !isPublicOldDotURL) {
	openOldDotLink(internalExpensifyPath);
	return;
	}
	openExternalLink(href);

openExternalLink hands that empty string to asyncOpenURL:

App/src/libs/actions/Link.ts

Lines 77 to 79 in df574e0

	function openExternalLink(url: string, shouldSkipCustomSafariLogic = false, shouldOpenInSameTab = false) {
	asyncOpenURL(Promise.resolve(), url, shouldSkipCustomSafariLogic, shouldOpenInSameTab);
	}

…and the web implementation bails on the first line because '' is falsy — this guard is exactly why nothing happens on click:

App/src/libs/asyncOpenURL/index.web.ts

Lines 12 to 15 in df574e0

	const asyncOpenURL: AsyncOpenURL = (promise, url, shouldSkipCustomSafariLogic, shouldOpenInSameTab) => {
	if (!url) {
	return;
	}

So this is not a TextLink rendering problem or a missing handler — the click fires correctly, but the URL it carries is empty. TransactionsImportedPage is the only consumer of ImportSpreadsheetColumns that omits learnMoreLink; categories, members, tags, multi-level tags, per diem, and company-cards imports all pass one, e.g.

App/src/pages/workspace/categories/ImportedCategoriesPage.tsx

Line 206 in df574e0

learnMoreLink={CONST.IMPORT_SPREADSHEET.CATEGORIES_ARTICLE_LINK}

and

App/src/pages/workspace/companyCards/addNew/CompanyCardsImportedPage.tsx

Line 188 in df574e0

learnMoreLink={CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL}

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

Two changes, both at the call-site / data layer — no behavior change for any other screen.

1. Add a help-article constant next to the existing *_ARTICLE_LINK entries in CONST.IMPORT_SPREADSHEET (

   App/src/CONST/index.ts

   Lines 8936 to 8943 in df574e0

   	IMPORT_SPREADSHEET: {
   	ICON_WIDTH: 180,
   	ICON_HEIGHT: 160,
   	CATEGORIES_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Create-categories#import-custom-categories',
   	MEMBERS_ARTICLE_LINK: 'https://help.expensify.com/articles/expensify-classic/workspaces/Invite-members-and-assign-roles#import-a-group-of-members',
   	TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags',
   	MULTI_LEVEL_TAGS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/workspaces/Create-expense-tags#import-multi-level-tags-from-a-spreadsheet',

   ), pointing at the dedicated personal-card import article: IMPORT_TRANSACTIONS_ARTICLE_LINK: 'https://help.expensify.com/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet'. That article already ships in the repo (docs/articles/new-expensify/connect-credit-cards/Import-Personal-Card-Transactions-From-a-Spreadsheet.md, titled "Import personal card transactions from a spreadsheet"), so no help-team content work is needed and it's the exact match for this flow.

2. Pass it through in TransactionsImportedPage — learnMoreLink={CONST.IMPORT_SPREADSHEET.IMPORT_TRANSACTIONS_ARTICLE_LINK} on the ImportSpreadsheetColumns instance at the permalink above. This is a one-line addition that brings the Wallet flow in line with every other importer.

I'd also harden the shared component so this can't silently recur: only render the TextLink when learnMoreLink is a non-empty string (a {!!learnMoreLink && …} guard around it in ImportSpreadsheetColumns). That's a small defensive change — any future caller that forgets the prop gets a clean sentence instead of a dead link. Existing callers are unaffected since they all pass a real URL.

No offline / optimistic / empty-state interactions here — this is a static href on a help link.

What alternative solutions did you explore? (Optional)

Reuse CONST.COMPANY_CARDS_CREATE_FILE_FEED_HELP_URL (the "Company Card Settings" article) instead of adding a new constant. Rejected: that article is about workspace company card feeds, while this flow imports a personal card in Wallet — pointing users there is misleading when a dedicated personal-card-import article already exists. The extra constant is one line and costs nothing.

Fix only the shared component (hide the link when learnMoreLink is empty) and not pass a URL at all. Rejected as a standalone fix: the reporter and the existing UX expect a working "Learn more" link, so removing it degrades the screen rather than fixing it. It's worth keeping as the defensive guard in change #3 above, paired with the real link — not as the whole answer.