Skip to content

Fix ESC key not returning to workspace list from workspace settings#86810

Closed
MelvinBot wants to merge 2 commits intomainfrom
claude-fixEscKeyWorkspaceSettings
Closed

Fix ESC key not returning to workspace list from workspace settings#86810
MelvinBot wants to merge 2 commits intomainfrom
claude-fixEscKeyWorkspaceSettings

Conversation

@MelvinBot
Copy link
Copy Markdown
Contributor

Explanation of Change

PR #86438 introduced WORKSPACE_NAVIGATOR as a new wrapper navigator on the root stack that nests WORKSPACES_LIST, WORKSPACE_SPLIT_NAVIGATOR, and DOMAIN_SPLIT_NAVIGATOR inside it. This broke the ESC key on workspace settings because MODAL_ROUTES_TO_DISMISS still contained WORKSPACE_SPLIT_NAVIGATOR (which is no longer a direct child of the root stack) instead of WORKSPACE_NAVIGATOR.

This PR:

  1. Replaces WORKSPACE_SPLIT_NAVIGATOR with WORKSPACE_NAVIGATOR in MODAL_ROUTES_TO_DISMISS so the dismiss modal action recognizes it.
  2. Adds special handling in handleDismissModalAction for WORKSPACE_NAVIGATOR: when the nested state index is > 0 (viewing a workspace/domain split), it pops within the navigator back to WORKSPACES_LIST instead of removing the entire navigator. When already at WORKSPACES_LIST (index 0), it pops the whole navigator normally.

Fixed Issues

$ #86785
PROPOSAL: #86785 (comment)

Tests

  1. Go to staging.new.expensify.com
  2. Go to the Workspaces tab
  3. Open any workspace (create one if needed)
  4. Press the ESC key
  5. Verify the app returns to the workspace list
  6. Press ESC again
  7. Verify the app exits workspace navigation entirely
  • Verify that no errors appear in the JS console

Offline tests

N/A - This is a navigation/keyboard shortcut fix that doesn't involve network requests.

QA Steps

  1. Go to the Workspaces tab
  2. Open any workspace
  3. Press the ESC key
  4. Verify the app returns to the workspace list
  5. Press ESC again
  6. Verify the app exits workspace navigation entirely
  • 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 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

N/A - Navigation logic change, no UI modification

Android: mWeb Chrome

N/A - Navigation logic change, no UI modification

iOS: Native

N/A - Navigation logic change, no UI modification

iOS: mWeb Safari

N/A - Navigation logic change, no UI modification

MacOS: Chrome / Safari

N/A - Navigation logic change, no UI modification

Replace WORKSPACE_SPLIT_NAVIGATOR with WORKSPACE_NAVIGATOR in
MODAL_ROUTES_TO_DISMISS since the split navigator is now nested
inside WORKSPACE_NAVIGATOR after PR 86438.

When the nested state index is > 0 (viewing a workspace/domain
split), pop within the navigator to WORKSPACES_LIST instead of
removing the entire navigator from the root stack.

Co-authored-by: Carlos Martins <luacmartins@users.noreply.github.com>
@luacmartins
Copy link
Copy Markdown
Contributor

luacmartins commented Mar 31, 2026

@luacmartins luacmartins marked this pull request as ready for review March 31, 2026 22:48
@luacmartins luacmartins requested a review from a team as a code owner March 31, 2026 22:48
@melvin-bot melvin-bot bot requested review from heyjennahay and sobitneupane and removed request for a team March 31, 2026 22:48
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Mar 31, 2026

@sobitneupane 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 March 31, 2026 22:48
@luacmartins luacmartins requested review from ZhenjaHorbach and removed request for sobitneupane March 31, 2026 22:48
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 31, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
...ateRootStackNavigator/GetStateForActionHandlers.ts 27.95% <0.00%> (-0.94%) ⬇️
... and 7 files with indirect coverage changes

…alAction

The new WORKSPACE_NAVIGATOR handling code returns a manually constructed
state object where lastRoute.state.routes can be PartialRoute[], making
the return type incompatible with StackNavigationState<ParamListBase>.
Adding an assertion resolves the typecheck failure.

Co-authored-by: Carlos Martins <luacmartins@users.noreply.github.com>
@MelvinBot MelvinBot requested a review from a team as a code owner March 31, 2026 22:59
@melvin-bot melvin-bot bot requested review from luacmartins and parasharrajat and removed request for a team March 31, 2026 22:59
@melvin-bot
Copy link
Copy Markdown

melvin-bot bot commented Mar 31, 2026

@parasharrajat @luacmartins One of you needs to 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]

@MelvinBot
Copy link
Copy Markdown
Contributor Author

Fixed the failing typecheck check.

Root cause: The new WORKSPACE_NAVIGATOR handling in handleDismissModalAction returns a manually constructed state object. lastRoute.state.routes has type PartialRoute[] | NavigationRoute[], making the return type incompatible with StackNavigationState<ParamListBase> (which requires NavigationRoute[]). This widened the inferred return type of RootStackRouter.getStateForAction, causing it to no longer match the PlatformStackRouterFactory parameter type expected by addRootHistoryRouterExtension.

Fix: Added a type assertion (as StackNavigationState<ParamListBase>) on the returned state object. This is safe because the base state is already StackNavigationState<ParamListBase> and we're only modifying the nested state of the last route.

@luacmartins luacmartins removed the request for review from parasharrajat March 31, 2026 23:01
@WojtekBoman
Copy link
Copy Markdown
Contributor

I'll take a look at it 👀

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

I'll take a look at it 👀

This fix works!
@WojtekBoman
But if you have a better idea, you can create a new PR!

@WojtekBoman
Copy link
Copy Markdown
Contributor

WojtekBoman commented Apr 1, 2026

Honestly, I think we shouldn't use Navigation.dismissModal to close non-modal pages, this PR adds some logic that it's not used for the main case of DISMISS_MODAL action, I would suggest to modify EscapeHandler and just use goBack when it's triggered from the workspace or domain page. I tested the following change:

diff --git a/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx b/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
index 2da8a369952..33023a568b2 100644
--- a/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
+++ b/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
@@ -2,9 +2,11 @@ import {useEffect} from 'react';
 import {useWideRHPState} from '@components/WideRHPContextProvider';
 import useOnyx from '@hooks/useOnyx';
 import KeyboardShortcut from '@libs/KeyboardShortcut';
-import Navigation from '@libs/Navigation/Navigation';
+import Navigation, {navigationRef} from '@libs/Navigation/Navigation';
 import CONST from '@src/CONST';
+import NAVIGATORS from '@src/NAVIGATORS';
 import ONYXKEYS from '@src/ONYXKEYS';
+import ROUTES from '@src/ROUTES';
 
 function EscapeHandler() {
     const [modal] = useOnyx(ONYXKEYS.MODAL);
@@ -39,6 +41,11 @@ function EscapeHandler() {
                     return;
                 }
 
+                if (navigationRef.getRootState()?.routes.at(-1)?.name === NAVIGATORS.WORKSPACE_NAVIGATOR) {
+                    Navigation.goBack(ROUTES.WORKSPACES_LIST.route);
+                    return;
+                }
+
                 Navigation.dismissModal();
             },
             shortcutConfig.descriptionKey,

and it works fine

@WojtekBoman
Copy link
Copy Markdown
Contributor

I wrote it quickly to check if it works, however this code might be improved, we can check exactly if it's called from Workspace or DomainSplitNavigator and dispatch pop action

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

ZhenjaHorbach commented Apr 1, 2026

Honestly, I think we shouldn't use Navigation.dismissModal to close non-modal pages, this PR adds some logic that it's not used for the main case of DISMISS_MODAL action, I would suggest to modify EscapeHandler and just use goBack when it's triggered from the workspace or domain page. I tested the following change:

diff --git a/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx b/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
index 2da8a369952..33023a568b2 100644
--- a/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
+++ b/src/libs/Navigation/AppNavigator/KeyboardShortcutsHandler/EscapeHandler.tsx
@@ -2,9 +2,11 @@ import {useEffect} from 'react';
 import {useWideRHPState} from '@components/WideRHPContextProvider';
 import useOnyx from '@hooks/useOnyx';
 import KeyboardShortcut from '@libs/KeyboardShortcut';
-import Navigation from '@libs/Navigation/Navigation';
+import Navigation, {navigationRef} from '@libs/Navigation/Navigation';
 import CONST from '@src/CONST';
+import NAVIGATORS from '@src/NAVIGATORS';
 import ONYXKEYS from '@src/ONYXKEYS';
+import ROUTES from '@src/ROUTES';
 
 function EscapeHandler() {
     const [modal] = useOnyx(ONYXKEYS.MODAL);
@@ -39,6 +41,11 @@ function EscapeHandler() {
                     return;
                 }
 
+                if (navigationRef.getRootState()?.routes.at(-1)?.name === NAVIGATORS.WORKSPACE_NAVIGATOR) {
+                    Navigation.goBack(ROUTES.WORKSPACES_LIST.route);
+                    return;
+                }
+
                 Navigation.dismissModal();
             },
             shortcutConfig.descriptionKey,

and it works fine

By the way, yes
Updating the keyboard listener sounds more logical to me too

@WojtekBoman
Copy link
Copy Markdown
Contributor

@ZhenjaHorbach I can prepare a PR with the change I described

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

@ZhenjaHorbach I can prepare a PR with the change I described

Go ahead!

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

@MelvinBot
Could you close this PR, please?

@MelvinBot
Copy link
Copy Markdown
Contributor Author

I can't close this PR based on this request. ZhenjaHorbach is not the PR author, an assignee, or a reviewer on this PR. To have me close it, the PR assignee (luacmartins) or someone with write access should make the request.

@ZhenjaHorbach
Copy link
Copy Markdown
Contributor

@MelvinBot
You are the author of this PR, and I'm a reviewer (C+) for this PR
So please, close your PR

@MelvinBot MelvinBot closed this Apr 1, 2026
@MelvinBot
Copy link
Copy Markdown
Contributor Author

Closed this PR as requested by reviewer ZhenjaHorbach.

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.

4 participants