Fix : Cards - In let's double check everything page, tapping device back button directs to cards page

[M00rish]

Explanation of Change

this change transforms the assigncard and addNewCard flow into routes/screen based flows instead of regular functional component steps to solve back button exiting the whole flow instead of going back to previous step.

Fixed Issues

$ #60018
PROPOSAL:
proposal

Tests

• Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

• 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
  • MacOS: Desktop
• 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

Expensify.Adhoc.mp4

Android: mWeb Chrome

Android_web.mp4

iOS: Native

iOS.webm

iOS: mWeb Safari

webios.mp4

MacOS: Chrome / Safari

Web.webm

Details

[codecov]

Codecov Report

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

Files with missing lines	Coverage Δ
src/ROUTES.ts	15.28% <100.00%> (+4.03%)	⬆️
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	75.00% <ø> (ø)
...s/workspace/companyCards/addNew/AmexCustomFeed.tsx	0.00% <ø> (ø)
...space/companyCards/addNew/CardInstructionsStep.tsx	0.00% <ø> (ø)
...ges/workspace/companyCards/addNew/CardNameStep.tsx	0.00% <ø> (ø)
...ges/workspace/companyCards/addNew/CardTypeStep.tsx	0.00% <ø> (ø)
...mpanyCards/addNew/DirectStatementCloseDatePage.tsx	0.00% <ø> (ø)
...s/workspace/companyCards/addNew/SelectBankStep.tsx	0.00% <ø> (ø)
...s/workspace/companyCards/addNew/SelectFeedType.tsx	0.00% <ø> (ø)
... and 14 more
... and 124 files with indirect coverage changes

[MarioExpensify]

@M00rish can you please check the ESLint and tests before we move forward with the adhoc build?

[M00rish]

fixed but main is failing as well.

[melvin-bot]

@Ollyws 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]

[heyjennahay]

No concern with product change

[M00rish]

👋 @Ollyws can you review please, there some activity on this logic these days, if conflicts appear again, will resolve after you review thanks!

[Krishna2323]

@Ollyws I’m interested in taking this over. Will try to start reviewing tomorrow.

[Krishna2323]

Reviewing...

[Krishna2323]

@M00rish could you please resolve the conflicts? Thanks!

[M00rish]

sure will resolve this today

[Krishna2323]

@M00rish the navigation flow is still broken on mWeb. The screen transitions from left to right when using the device back button, and from right to left when using the app back button. The steps are also not in sync — sometimes it navigates to the next step instead of the previous one when using the device back button, and in worse cases it skips multiple steps when going back.

Also, @MarioExpensify, I want to confirm that we’re okay with the new UX behavior where screens transition left to right (or vice versa) during navigation. Previously, only the step changed and no screen was added or removed (no screen transition).

Monosnap.screencast.2025-12-16.11-17-36.mp4

Monosnap.screencast.2025-12-16.11-56-44.mp4

[M00rish]

The steps are also not in sync — sometimes it navigates to the next step instead of the previous one when using the device back button, and in worse cases it skips multiple steps when going back.

the navigation hook is linked to onyx state, it's not always starting from the beginning in main, sometimes it skips depending on the onyx state, will review and comeback...

The screen transitions from left to right when using the device back button, and from right to left when using the app back button.

will check it.

[M00rish]

this work was done here already, so i think can be closed by now.

[MarioExpensify]

Okay, closing the PR and the issue. Thank you for your work on this @M00rish.