Fix: TestToolsModal is not fading in on web

[chrispader]

@parasharrajat

Explanation of Change

On web, the TestToolsModal should have a fading in animation, rather than sliding in from the right. This PR adds the missing animation option on the screen.

Fixed Issues

$ #65932
PROPOSAL: #65245 (comment)

Tests

• Verify that no errors appear in the JS console

1. Open the app
2. Press CMD+D (or Cntrl+D on Windows/Linux) to open the test tools
3. Make sure the modal is fading in instead of sliding in from the right.

Offline tests

Not needed.

QA Steps

• Verify that no errors appear in the JS console

Same as in Tests.

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 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: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2025-07-07.at.01.07.20.mov

Screen.Recording.2025-07-07.at.01.06.55.mov

MacOS: Desktop

[melvin-bot]

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

[parasharrajat]

I will get on it tomorrow

[parasharrajat]

Android: There is a related problem with test-modal on native. It is sometimes not scrollable. Let's fix that too. This is a real device.

Screenrecorder-2025-07-07-11-35-46-326-2025-07-07.06_09_26.943.mp4

[parasharrajat]

Bump @chrispader

[chrispader]

Android: There is a related problem with test-modal on native. It is sometimes not scrollable. Let's fix that too. This is a real device.

Screenrecorder-2025-07-07-11-35-46-326-2025-07-07.06_09_26.943.mp4

@parasharrajat i can repro the issue, though this is not related to my changes in this PR. Working on a fix!

[chrispader]

Used the chance to add a new contentStyle property to the Platform Stack Navigation and do some simple refactoring.

[chrispader]

@parasharrajat after some testing, i could not find a quick fix as this seems to be either a react-native or react-navigation internal issue.

Can we handle this in a separate follow-up PR? I only have limited availability this month and this PR was originally only thought as a quick fix to the issue you mentioned in the other PR

[parasharrajat]

Sure, if we do not have go to fix for this problem, we can solve it in a different issue. But I see that you have done some refactoring around modals. Do you think those are needed for this issue? If not, I would say we revert those otherwise, we will have to extend the scope of the testing for this PR to cover other Modals and possibility of regressions will also increase.

We are already working on other modal refactoring PRs, do you think these changes are more suited for those? @chrispader

[parasharrajat]

I see we already have an issue for scrolling #64550

[parasharrajat]

@chrispader Bump.

[chrispader]

@parasharrajat changes reverted, i will open a follow-up PR for the Platform Stack Navigation changes and refactoring

[parasharrajat]

Screenshots

🔲 iOS / native

🔲 iOS / Safari

07.07.2025_11.00.16_REC.mp4

🔲 MacOS / Desktop

07.07.2025_10.54.45_REC.mp4

🔲 MacOS / Chrome

07.07.2025_10.52.08_REC.mp4

🔲 Android / Chrome

07.07.2025_10.59.57_REC.mp4

🔲 Android / native

[github-actions]

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

[github-actions]

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

[parasharrajat]

@chrispader Let's attach #65932 to this PR.

[github-actions]

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

Android 🤖	iOS 🍎
⏩ SKIPPED ⏩	❌ FAILED ❌
The build for Android was skipped	The QR code can't be generated, because the iOS build failed

Desktop 💻	Web 🕸️
⏩ SKIPPED ⏩	⏩ SKIPPED ⏩
The build for Desktop was skipped	The build for Web was skipped

---

👀 View the workflow run that generated this build 👀

[chrispader]

@chrispader Let's attach #65932 to this PR.

done!

[github-actions]

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

[github-actions]

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

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

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/65535/NewExpensify.dmg	https://65535.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[parasharrajat]

I am not able to test this. Why are native builds failing? @chrispader

[chrispader]

Ahh @parasharrajat i just merged main and apparently this change has just already been changed in #64717

Will close this PR!