Skip to content

Fix card-issued link resolving against the active route - #98406

Merged
roryabraham merged 25 commits into
Expensify:mainfrom
mukhrr:fix/95364
Sep 4, 2026
Merged

roryabraham merged 25 commits into
Expensify:mainfrom
mukhrr:fix/95364

Conversation

@mukhrr

@mukhrr mukhrr commented Aug 12, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

The admin "replacement card" link (and the Spend > Chat card link) could open "Not Here" after a few clicks. getCardIssuedMessage built the link with createDynamicRoute and no base path, so it used Navigation.getActiveRoute(); when the chat message re-rendered while the card-details RHP was open, the href was rebuilt against the RHP's route and stopped resolving. The fix binds the link to the component's own screen via a new useDynamicRoute hook (built on React Navigation's useRoutePath()), so the href stays correct regardless of the active route.

Fixed Issues

$ #95364
PROPOSAL: #95364 (comment)

Tests

  1. Sign in as a workspace admin and make sure the Expensify Card feature is enabled on the workspace.
  2. Issue a virtual card to yourself, then go to Account > Wallet > Virtual card > Report virtual card fraud so a replacement virtual card is issued.
  3. Open the workspace chat and locate the "replacement card" hyperlink.
  4. Click the "replacement card" link → the card details open in the RHP.
  5. Close the card details and click the "replacement card" link again (repeat a few times).
  6. Verify it opens the card details every time and never shows the "Not Here" page.
  7. Open the same report from the Spend tab (Spend > Chat) and repeat steps 4-6, verifying the same.
  • Verify that no errors appear in the JS console

Offline tests

Same as Tests. The link is built client-side, so the behavior is identical offline.

QA Steps

  1. Issue a virtual card for yourself.
  2. Go to Account > Wallet > Virtual card > Report virtual card fraud.
  3. Go to the workspace chat and click the "replacement card" hyperlink a few times.
  4. Verify the app opens the card details and never shows the "Not Here" page.
  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
android_app.mp4
Android: mWeb Chrome
android_web.mp4
iOS: Native
IOS-app.mp4
iOS: mWeb Safari
IOS-web.mp4
MacOS: Chrome / Safari
web.mp4

@mukhrr
mukhrr marked this pull request as ready for review August 12, 2026 10:05
@mukhrr
mukhrr requested review from a team as code owners August 12, 2026 10:05
@melvin-bot
melvin-bot Bot requested a review from dmkt9 August 12, 2026 10:05
@mukhrr
mukhrr marked this pull request as draft August 12, 2026 10:05
@melvin-bot
melvin-bot Bot requested review from trjExpensify and removed request for a team and trjExpensify August 12, 2026 10:05
@melvin-bot

melvin-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

@dmkt9 Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team August 12, 2026 10:05
@codecov

codecov Bot commented Aug 12, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/ROUTES.ts 27.52% <ø> (+0.08%) ⬆️
src/components/ReceiptAlternativeMethods.tsx 100.00% <100.00%> (ø)
...c/components/ReportActionItem/IssueCardMessage.tsx 91.66% <100.00%> (+0.36%) ⬆️
src/components/ReportWelcomeText.tsx 96.72% <100.00%> (ø)
src/hooks/useScreenBoundDynamicRoute.ts 100.00% <100.00%> (ø)
...n/helpers/dynamicRoutesUtils/createDynamicRoute.ts 100.00% <ø> (ø)
src/libs/ReportAlternateTextUtils.ts 87.61% <100.00%> (ø)
...es/inbox/report/ContextMenu/ContextMenuActions.tsx 40.34% <ø> (ø)
src/components/BookTravelButton.tsx 85.13% <50.00%> (+0.20%) ⬆️
src/libs/ReportActionsUtils.ts 81.74% <0.00%> (ø)
... and 9 more
... and 12 files with indirect coverage changes

@mukhrr
mukhrr force-pushed the fix/95364 branch 2 times, most recently from 4affc1c to 0d92b1f Compare August 12, 2026 10:25
@mukhrr
mukhrr marked this pull request as ready for review August 12, 2026 10:26
Comment thread tests/unit/ReportActionsUtilsTest.ts Resolved
getCardIssuedMessage built the admin card-details link with createDynamicRoute
and no base path, so it prepended Navigation.getActiveRoute(). The href is
rebuilt on every render, so an Onyx-driven re-render while an RHP is open over
the chat rebuilt it against the RHP's route and it fell through to Not Here.

Base the link on the component's own screen via React Navigation's useRoutePath,
wrapped in a new useDynamicRoute hook that returns a createDynamicRoute bound to
that path. The href is now identical on every render regardless of the active
route, and Spend > Chat is covered by the same change.
# Conflicts:
#	src/components/ReportActionItem/IssueCardMessage.tsx
#	src/pages/inbox/report/ContextMenu/ContextMenuActions.tsx
#	tests/unit/ReportActionsUtilsTest.ts
@dmkt9

dmkt9 commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

@mukhrr The solution looks good. However, I think we should verify all usages of createDynamicRoute and replace them with useDynamicRoute where necessary.

@mukhrr

mukhrr commented Aug 17, 2026

Copy link
Copy Markdown
Contributor Author

@dmkt9 I did!

@mukhrr The solution looks good. However, I think we should verify all usages of createDynamicRoute and replace them with useDynamicRoute where necessary.

@dmkt9

dmkt9 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@dmkt9 I did!

@mukhrr I'm not sure. I did a quick search and found a few places that still need to be updated:

Navigation.navigate(createDynamicRoute(DYNAMIC_ROUTES.TRAVEL_UPGRADE.path));

const contactMethodsHref = `${environmentURL}${addLeadingForwardSlash(createDynamicRoute(DYNAMIC_ROUTES.CONTACT_METHODS.path))}`;

const reportDetailsPath = reportRHPActiveRoute ? createDynamicRoute(DYNAMIC_ROUTES.REPORT_DETAILS.path, reportRHPActiveRoute) : createDynamicRoute(DYNAMIC_ROUTES.REPORT_DETAILS.path);

I think there are still many other usages that we need to check.

@mukhrr

mukhrr commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@dmkt9 actually we have 477 createDynamicRoute calls in src/ as I mentioned before and I think 471 are fine already. 146 pass an explicit base, and 325 run at press time inside navigate / goBack, where the active route is the correct one and is the documented usage in NAVIGATION.md. Only the ones built during render and used later can go stale.

Fixed only 6 with exact reason:

  • ReceiptAlternativeMethods.tsx:38
  • ReportWelcomeText.tsx:102
  • MergeResultPage.tsx:81
  • DynamicReconciliationAccountSettingsPage.tsx:159
  • companyCards/utils.tsx:246 and :373

The first four use useDynamicRoute now. The last two only needed the backTo the function already takes, same as the QBO and Sage Intacct branches right beside them, leftover from #72352.

The four component/page sites built an href during render with no base path, so a
re-render while another route was on top rebuilt the link against that route. They
now take the base from useDynamicRoute.

getExportMenuItem is not a hook context; its NetSuite and QuickBooks Desktop
branches simply never read the backTo the function already accepts, unlike the
QuickBooks Online and Sage Intacct branches beside them.

ReportWelcomeText's getReportRHPActiveRoute workaround was a no-op: it returns
getActiveRoute() when a report is in the RHP and an empty string otherwise, so both
branches resolved to the same base as passing none.
@dmkt9

dmkt9 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@mukhrr I agree that we don't need to change the cases where createDynamicRoute is called inside onPress or onSelected callbacks. But what about cases where navigate is called inside a useEffect, like in BookTravelButton?

Couldn't that potentially trigger when the screen isn't focused?

@mukhrr

mukhrr commented Aug 18, 2026

Copy link
Copy Markdown
Contributor Author

@dmkt9 I believe BookTravelButton cases run inside the bookATrip press handler, so they are not affected.

@dmkt9

dmkt9 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@dmkt9 I believe BookTravelButton cases run inside the bookATrip press handler, so they are not affected.

useEffect(() => {
if (!shouldResumeBookingRef.current || areTravelPersonalDetailsMissing(privatePersonalDetails)) {
return;
}
shouldResumeBookingRef.current = false;
bookATrip();
// eslint-disable-next-line react-hooks/exhaustive-deps -- we only want to trigger this effect when privatePersonalDetails changes
}, [privatePersonalDetails]);

@mukhrr
mukhrr requested a review from dmkt9 August 31, 2026 12:20
@roryabraham

Copy link
Copy Markdown
Contributor

@mukhrr sounds reasonable to address in a follow-up. Feel free to report the issue separately

@mukhrr

mukhrr commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

@mukhrr sounds reasonable to address in a follow-up. Feel free to report the issue separately

@roryabraham hmm can you pls have melvin to open a new issue and assign me and @dmkt9 ?! leaving Reproduction steps here:

  1. Go to any expense report details
  2. Click "Add your number" link

Expected: Background should stay on as-is

Actual: Background navigates to user /profile page

REC-20260903105740.mp4

@roryabraham

Copy link
Copy Markdown
Contributor

@MelvinBot create an issue per the last comments. Assign @mukhrr @dmkt9 @roryabraham

@MelvinBot

Copy link
Copy Markdown
Contributor

Created #100260 — "Contact methods RHP swaps the background tab to Account > Profile".

It carries mukhrr's reproduction steps, the video, the RCA (DYNAMIC_CONTACT_METHODS pinned to SETTINGS.PROFILE.ROOT in SETTINGS_TO_RHP, so getMatchingFullScreenRoute wins before the dynamic base-path branch), and the proposed fix (drop it from the relations, same as DYNAMIC_IMPORTED_MEMBERS_ROLE).

Assignees: only roryabraham is assigned. GitHub rejected mukhrr and dmkt9 because both have read-only access on Expensify/App — assignment requires write access or a prior comment on the issue. I tagged them both on the issue so they get notified; once either comments, an internal engineer can add them with gh issue edit 100260 --repo Expensify/App --add-assignee mukhrr --add-assignee dmkt9.


view run

@mukhrr

mukhrr commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

@dmkt9 let's continue pls

@dmkt9

dmkt9 commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. 🎉

Reviewed commit: 66e92cf136

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/ROUTES.ts Resolved
@dmkt9

dmkt9 commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
chrome.mp4

@mukhrr
mukhrr requested a review from dmkt9 September 3, 2026 08:45
@mukhrr

mukhrr commented Sep 3, 2026

Copy link
Copy Markdown
Contributor Author

@dmkt9 anything else here?

@dmkt9 dmkt9 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@melvin-bot
melvin-bot Bot requested a review from roryabraham September 3, 2026 14:48
@roryabraham
roryabraham merged commit 5c08345 into Expensify:main Sep 4, 2026
35 of 37 checks passed
@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@github-actions

github-actions Bot commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #98406.

Android 🤖 iOS 🍎
❌ FAILED ❌ ❌ FAILED ❌
The QR code can't be generated, because the Android build failed The QR code can't be generated, because the iOS build failed
Web 🕸️
https://98406.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@OSBotify

OSBotify commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.73-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

@MelvinBot

MelvinBot commented Sep 7, 2026 •

Copy link
Copy Markdown
Contributor

No help site changes are required for this PR, so I did not create a draft PR.

This is an internal navigation fix with no user-facing surface change. The card-issued hyperlink was always meant to open the card details; it was just resolving against the wrong route and landing on "Not here". After the fix it does what the product already promised, so there is no documented behavior to correct or add.

Why I concluded no docs are needed

What actually changed — all 24 files are code and tests. No docs/ files and no src/languages/* files are touched, so no user-facing copy, label, button, or tab name changed:

  • src/hooks/useScreenBoundDynamicRoute.ts — new internal hook that binds a dynamic route to its own screen instead of Navigation.getActiveRoute().
  • src/ROUTES.ts:1197-1207 — adds SCREENS.SEARCH.ROOT as an entry screen for the existing EXPENSIFY_CARD_DETAILS route. No new route and no new page.
  • The remaining files thread buildDynamicRoute through call sites in place of createDynamicRoute.

Help articles I checked. The articles that mention replacement cards all document how to request one, which this PR does not change:

  • docs/articles/new-expensify/expensify-card/How-to-Request-a-New-Expensify-Card.md
  • docs/articles/new-expensify/expensify-card/Disputing-Expensify-Card-Transactions.md
  • docs/articles/new-expensify/expensify-card/Update-Your-Expensify-Card-Mailing-Address.md
  • docs/articles/expensify-classic/expensify-card/Request-the-Expensify-Card.md

None of them describe the in-chat "replacement card" hyperlink, the card details view, or the "Not here" page. There is no stale statement to fix and no new step to document — a reader following any of these articles gets the same instructions before and after this PR.

Why I did not write a new article. Per HELP_AUTHORING_GUIDELINES.md, help content covers what a customer needs to do in the product. A bug fix that restores a link's intended destination gives a customer nothing new to do, so documenting it would add noise rather than help.

I skipped the label and assignment steps as well, since they only apply to a docs PR.

@mukhrr, there is no help site PR to review. If you expected a specific article to change — for example if this fix also changed where the link lands compared to its original intended destination — tell me which article and I will draft the update.


view run · view recording

@OSBotify

OSBotify commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.73-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants