[Due for payment 2026-09-04] Android - Company cards - "guide" in Help guide link is not tappable

[applause-bot]

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

---

Version Number: 9.4.63-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #99033
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Workspace Settings

Action Performed:

Precondition:

• Set device font size to minimum.

1. Launch Expensify app.
2. Go to workspace settings > Company cards.
3. Tap Add cards.
4. Select United States > Next.
5. Select Import transactions from files > Next.
6. Tap "guide" in Help guide link.

Expected Result:

"guide" in Help guide link will be tappable.

Actual Result:

"guide" in Help guide link is not tappable.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7244712_1787873257220.Screen_Recording_20260828_072122_Expensify.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7244712

Issue Owner

Current Issue Owner: @nyomanjyotisa

[applause-bot]

While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/e0061fe51f6bda121661e34f2e0ca3ba059d2004ebbf00b328086182f92688dd

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #99033

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[melvin-bot]

@youssef-lr @nyomanjyotisa you have been assigned to this deploy blocker because you reviewed the offending PR: #99033

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[MelvinBot]

Deploy Blocker Analysis

Confirmed: PR #99033 introduced this. melvin-bot's auto-assignment is correct — that PR rewrote the exact "Help guide" text in the exact flow named in the bug, it's in the current StagingDeployCash, and the bug is staging-only (fresh regression). Confidence: High.

Root cause: #99033 replaced the old RenderHTML anchor with a plain <Text> that has inline-nested <TextLink> children. The "guide" link is one of them:

• ImportFromFileStep.tsx:92-98 — the composed <Text> block
• ImportFromFileStep.tsx:96 — the offending "guide" link
• TextLink.tsx:70-85 — TextLink is just a <Text onPress> (no Pressable, no hitSlop, no padding)

On Android, a pressable Text nested inline inside another Text only receives touches within the actual glyph bounding box of its characters — it doesn't get promoted to a native touch target and gets no hitSlop/padding expansion. At minimum device font size the word "guide" shrinks to a few px tall, so its hit area collapses below a reliably-tappable threshold. iOS composes nested Text press ranges more generously, and at normal font sizes the glyph box is big enough — which is why this reproduces only on Android at minimum font size and slipped through the PR's cross-platform screenshots.

Recommended fix: roll forward (don't revert). Reverting #99033 is disproportionate — it would tear out a shipped feature (always-visible mapping fields + template download across many files) to fix one untappable link. Preferred targeted fix:

1. Restore RenderHTML for just the help text (lowest risk — back to the known-good anchor rendering). Only revert the createFileFeedHelpText rendering at lines 92-98 to a RenderHTML call and restore the language strings to the single <muted-text><a> HTML form. This also covers the sibling "template" TextLink at line 94, which has the same defect but is redundant with the full-width "Download our template" button below.
2. Alternatively, keep the composed layout but give the link a real touch target on Android (Pressable/hitSlop) — higher risk of missing an edge case than option 1.

Notes on labels / testing

• Labels/assignees: No change needed — DeployBlockerCash is correct for a frontend bug, and the two approving reviewers of the causing PR are already assigned.
• Testing: This is Android-only at minimum font size; it can't be reproduced on the web build, so no App test run is attached. Root cause is confirmed directly from the diff.

---

Next Steps: Reply with @MelvinBot implement this to have me open a draft PR for option 1, or @MelvinBot <feedback> to refine.

---

view run