fix: Import - Blank RHP opens when pressing ESC key after importing spreadsheet.

[Krishna2323]

Explanation of Change

Fixed Issues

$ #56936
PROPOSAL: #56936 (comment)

Tests

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Click 3-dot menu > Import spreadsheet.
4. Click Upload.
5. Select a file.
6. Map the columns and click Import.
7. Click Got it.
8. Press ESC key/Use back button or swipe right on native devices.
9. Repeat step 2 to 8 by importing members, tags, and per diem rates.

• Verify that no errors appear in the JS console

Offline tests

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Click 3-dot menu > Import spreadsheet.
4. Click Upload.
5. Select a file.
6. Map the columns and click Import.
7. Click Got it.
8. Press ESC key/Use back button or swipe right on native devices.
9. Repeat step 2 to 8 by importing members, tags, and per diem rates.

QA Steps

1. Go to staging.new.expensify.com
2. Go to workspace settings > Categories.
3. Click 3-dot menu > Import spreadsheet.
4. Click Upload.
5. Select a file.
6. Map the columns and click Import.
7. Click Got it.
8. Press ESC key/Use back button or swipe right on native devices.
9. Repeat step 2 to 8 by importing members, tags, and per diem rates.

• 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 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 verified the translation was requested/reviewed 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.js 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 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.
• 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_native.mp4

Android: mWeb Chrome

android_chrome.mp4

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

desktop_app.mp4

MacOS: Desktop

desktop_app.mp4

[melvin-bot]

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

[Krishna2323]

Sorry, this isn't ready yet, I need to upload the recordings.

[Krishna2323]

@jayeshmangwani, I found a navigation issue while recording videos, which also occurs after applying changes from this PR.

Problem: If you have more than one RHP open at a time and close it by clicking outside the modal, you need to click the browser back button twice to return to the previous route. This happens with all RHP pages. You can reproduce the issue using the following steps:

Policy Tags Pages:

1. Click on a tag > Select GL code > Click on the backdrop.
2. Press the browser back button.

Policy Workflows Pages:

1. Click on Add approval workflow > Select a member and click Next > Click on the backdrop.
2. Press the browser back button.

On android chrome after this PR

android_chrome.mp4

On workflows page

Monosnap.screencast.2025-02-27.06-28-21.mp4

Please let me know how we should handle this. Should we address it, or leave it as it is since this appears to be an app-wide behavior?

[jayeshmangwani]

I think we could leave it as is for now since this issue is also reproducible in the production version. However, we could also open a new issue to investigate further. I'm not entirely sure—I’m leaning on @yuwenmemon here. What do you think about this issue?

[Krishna2323]

@yuwenmemon friendly bump.

[jayeshmangwani]

@Krishna2323, I’m facing an issue on mWeb Safari. Please let me know if you can reproduce this as well.

Steps to reproduce:

1. Go to Workspace → Categories → Import Categories
2. Choose a file and press Import
3. Press Got it on the modal
4. You’ll land on the Categories page
5. Swipe to go back to the previous page – here, the Categories page is displayed again, resulting in it appearing twice

bug-categoties-page-twice.mov

[jayeshmangwani]

@Krishna2323 can you please check this and confirm if we can fix it?

[Krishna2323]

Sorry for the delay, @jayeshmangwani 🙏🏻. I was busy with this high-priority PR (#54165). I will check this issue today.

[Krishna2323]

Currently trying to find a solution for this issue.

[yuwenmemon]

I think we could leave it as is for now since this issue is also reproducible in the production version.

Yeah that's fine. We can file a bug report for a follow-up.

[Krishna2323]

@jayeshmangwani, I tried to find a solution for this issue, but unfortunately, I couldn't find one. I highly suspect that it is related to this issue because if we click the browser's back button once and then swipe back, it returns to the correct page.

[Krishna2323]

@jayeshmangwani, friendly bump to check this comment.

[jayeshmangwani]

@Krishna2323 I think we should fix this in this PR. It’s not ideal to proceed with the bug where the Categories page reappears if we swipe back. @yuwenmemon, what do you think about this #57502 (comment)?

[Krishna2323]

@jayeshmangwani, honestly, I have tried my best to find a solution for this issue, but unfortunately, I couldn't find one. This seems to be a very niche bug occurring only on iOS Safari. Please let me know if you have any plans. Thanks!

[jayeshmangwani]

I couldn't find one. This seems to be a very niche bug occurring only on iOS Safari

@Krishna2323 My iOS build is currently broken, so I can’t confirm this myself. Could you please check if iOS is working fine? Video would be helpful.

[Krishna2323]

@jayeshmangwani

Monosnap.screencast.2025-03-24.20-02-53.mp4

[jayeshmangwani]

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: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• 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 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
  • 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 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)
• 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
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately and each prop has a /** comment above it */
  • The file is named correctly
  • 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
  • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
  • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
  • All JSX used for rendering exists in the render method
  • 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 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 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.
• 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: Native

Android.mov

Android: mWeb Chrome

mweb-safari.mov

iOS: Native

iOS.mov

iOS: mWeb Safari

mweb-chrome.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

[jayeshmangwani]

@yuwenmemon We are experiencing this issue only on mWeb Safari, but it is also occurring on other pages in Safari. Therefore, I think we should open an issue for this.

[jayeshmangwani]

LGTM 🚀

[OSBotify]

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

[github-actions]

🚀 Deployed to staging by https://github.com/yuwenmemon in version: 9.1.20-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	success ✅

[mallenexpensify]

This PR was linked in this deploy blocker
mWeb - Workspace - Back button is irresponsive after importing

@Krishna2323 @jayeshmangwani , can you review and comment on the issue? thx

[github-actions]

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.20-2 🚀

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