[UX Reliability] Use new modal in `BaseReportActionContextMenu` #56606

BartoszGrajdek · 2025-02-10T14:52:09Z

Explanation of Change

We've decided to refactor the react-native-bottom-modal code so that it utilizes react-native-reanimated, our goal was to improve FPS, remove the outdated library and gradually switch to the new solution. This PR enables the new solution in BaseReportActionContextMenu.

Fixed Issues

$ #49354

Tests

I think testing should go like this:

Open the modal.
Close it by clicking the backdrop.
Open the modal.
Close it through the "back" button if it exists on your device.
Open the modal.
Go through each button/option in that modal and verify that everything's functioning properly.

To open the modal you need to:

Open any chat
Send a message
Long-press on the message you've sent

Offline tests

Same as above, but it shouldn't matter

QA Steps

Same as above

PR Author Checklist

Screenshots/Videos

Android: Native

Android.mov

Android: mWeb Chrome

Android.-.mWeb.mov

iOS: Native

iOS.mov

iOS: mWeb Safari

iOS.-.mWeb.mov

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

…dit-modal

melvin-bot · 2025-03-04T13:57:23Z

@shawnborton @ZhenjaHorbach 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]

blazejkustra · 2025-03-04T14:12:08Z

@ZhenjaHorbach I'll be handling this PR, so if anything comes up, please let me know!

shawnborton · 2025-03-04T15:14:11Z

Looks like the popover launches in the wrong spot on web for a split second:

ZhenjaHorbach · 2025-03-04T15:45:32Z

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

Screenrecorder-2025-03-29-08-46-01-658.mp4

Android: mWeb Chrome

Screenrecorder-2025-03-29-08-50-23-240.mp4

iOS: Native

2025-03-29.08.55.40.mp4

iOS: mWeb Safari

2025-03-29.08.55.37.mp4

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

ZhenjaHorbach · 2025-03-04T15:47:25Z

Looks like the popover launches in the wrong spot on web for a split second:

Confirm !
I also sometimes have this bug

ZhenjaHorbach · 2025-03-04T15:55:32Z

Also looks like a bug
That we have animation after changing the size of the modal

2025-03-04.16.54.42.mov

ZhenjaHorbach · 2025-03-04T16:06:14Z

On Ios-web and Android-web I have a mini context menu

blazejkustra · 2025-03-05T14:56:49Z

I'll come back to this later this week or next week as I have projects with higher priority, sorry!

shawnborton · 2025-03-25T11:51:33Z

Any update here?

ZhenjaHorbach · 2025-03-25T15:31:38Z

I suppose we will continue to work on this soon !

#49354 (comment)

…new-edit-modal

blazejkustra · 2025-03-28T13:47:53Z

Looks like the popover launches in the wrong spot on web for a split second:

Confirm ! I also sometimes have this bug

@ZhenjaHorbach Could you retest? I can't reproduce this

blazejkustra · 2025-03-28T13:58:53Z

Also looks like a bug That we have animation after changing the size of the modal

2025-03-04.16.54.42.mov

Same with this, looks like it works correct now @ZhenjaHorbach

ZhenjaHorbach · 2025-03-28T14:17:13Z

Sure !
I will recheck soon !

blazejkustra · 2025-03-28T14:34:17Z

On Ios-web and Android-web I have a mini context menu

@ZhenjaHorbach Should be fixed as well

blazejkustra · 2025-03-28T14:35:55Z

Bear in mind that we are only migrating modals of type bottom_docked:

Popovers shouldn't be affected at all:

ZhenjaHorbach · 2025-03-28T14:46:49Z

Remove unused import from BaseReportActionContextMenu

Actually this issue is similar to this

#58705

ZhenjaHorbach · 2025-03-28T16:39:58Z

Checked my old videos
And notice that we don't have a closing animation now

2025-03-28.17.38.30.mov

blazejkustra · 2025-03-28T16:45:16Z

And notice that we don't have a closing animation now

Hmm interesting, that's definitely a blocker. I'm going to look at it on Monday!

Any other bugs/issues? @ZhenjaHorbach

ZhenjaHorbach · 2025-03-28T16:48:15Z

And notice that we don't have a closing animation now

Hmm interesting, that's definitely a blocker. I'm going to look at it on Monday!

Any other bugs/issues? @ZhenjaHorbach

No

Otherwise everything is good !

And If you have 5 minutes
Could you please try to reproduce on your simulator to make sure ?

ZhenjaHorbach · 2025-03-28T16:59:08Z

And interesting
Even animationOutTiming is not working

blazejkustra · 2025-03-28T17:04:23Z

And interesting Even animationOutTiming is not working

It was working — the issue was that the content was disappearing and the modal was shrinking in a weird way. It should work now after the last two commits.

blazejkustra · 2025-03-28T17:05:52Z

You can check again, this time it should work well on all platforms, I'm logging off. Have fun! 😄

ZhenjaHorbach · 2025-03-28T17:07:19Z

You are fast 😅
And yes
It works
Thanks for fix !

blazejkustra · 2025-03-28T17:08:31Z

That's what I do for a living 🏃‍♂️💨

ZhenjaHorbach · 2025-03-28T17:20:33Z

@mountiny
Could you please help with adhoc builds here to make sure that everything works good ?

ZhenjaHorbach · 2025-03-28T17:33:13Z

But on the other hand, I think everything will be fine in adhoc builds
The only thing that confuses me is the delay when changing the color of the status bar
But the same issue is in staging

2025-03-28.18.31.42.mov

github-actions · 2025-03-28T22:12:58Z

🚧 @mountiny has triggered a test app build. You can view the workflow run here.

github-actions · 2025-03-28T22:43:41Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
Android 🤖🔄	iOS 🍎🔄
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/56606-hybrid/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/56606-hybrid/index.html

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

👀 View the workflow run that generated this build 👀

ZhenjaHorbach · 2025-03-29T07:58:45Z

LGTM !

ZhenjaHorbach · 2025-03-29T08:09:48Z

But wait
On real device notice this
And this is not reproduced in simulators

2025-03-29.09.08.12.mp4

mountiny · 2025-03-30T23:09:29Z

@blazejkustra can you please check that out? Thanks!

blazejkustra · 2025-03-31T12:43:54Z

Is this iOS? What browser are you using?@ZhenjaHorbach

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-03-31.at.14.42.52.mp4

mountiny · 2025-03-31T12:46:02Z

seems like normal safari to me

ZhenjaHorbach · 2025-03-31T12:50:28Z

Yes
It's a default safari !

blazejkustra · 2025-03-31T14:44:30Z

I can’t reproduce it 😢

Could you write out the detailed steps? I want to make sure I’m doing it the same way. Also, could you let me know which iPhone model you’re using, the iOS version, and the version of Safari? That’ll help a lot—thanks! @ZhenjaHorbach

ZhenjaHorbach · 2025-03-31T14:56:40Z

I can’t reproduce it 😢

Could you write out the detailed steps? I want to make sure I’m doing it the same way. Also, could you let me know which iPhone model you’re using, the iOS version, and the version of Safari? That’ll help a lot—thanks! @ZhenjaHorbach

Hmmm, good question.
Could you try using a video message for testing?

First, tap on the input.
Then, hold down the video to open a modal.
Next, tap outside the modal window to close it.
Repeat this several times.

I just tested it, and it works for me!

blazejkustra · 2025-03-31T15:10:19Z

I just tested it, and it works for me!

Wait - you mean it doesn't work for you when following these steps, right? 😆

First, tap on the input.
Then, hold down the video to open a modal.
Next, tap outside the modal window to close it.
Repeat this several times.

Still no luck, tried several times:

ScreenRecording_03-31-2025.17-05-38_1.MP4

could you let me know which iPhone model you’re using, the iOS version, and the version of Safari?

@ZhenjaHorbach bump 😄

blazejkustra · 2025-03-31T15:15:31Z

@mountiny Can you try? 😂 56606.pr-testing.expensify.com

ZhenjaHorbach · 2025-03-31T15:25:12Z

Wait - you mean it doesn't work for you when following these steps, right?

It reproduces stably for me following these steps 😅

could you let me know which iPhone model you’re using, the iOS version, and the version of Safari?

Oh
Sorry
I have iPhone 13 18.3.1 (18.4 - the same issue)

ZhenjaHorbach · 2025-03-31T16:23:34Z

By the way, I also have Chrome on my iPhone
I can also reproduce

And I can reproduce with any message

2025-03-31.18.25.35.mp4

BartoszGrajdek added 6 commits February 10, 2025 15:47

feat: enable new modal in report action context menu

9d21c42

fix: slide out animation not appearing

4cb6e96

fix: eslint issues

59900cf

fix: type mismatch

4e65f7d

Merge remote-tracking branch 'origin/main' into @BartoszGrajdek/new-e…

31b78ca

…dit-modal

Merge remote-tracking branch 'origin/main' into @BartoszGrajdek/new-e…

82e2740

…dit-modal

BartoszGrajdek marked this pull request as ready for review March 4, 2025 13:57

BartoszGrajdek requested a review from a team as a code owner March 4, 2025 13:57

melvin-bot bot requested review from shawnborton and ZhenjaHorbach and removed request for a team March 4, 2025 13:57

Merge branch 'main' of github.com:Expensify/App into @BartoszGrajdek/…

39323cb

…new-edit-modal

Remove unused import from BaseReportActionContextMenu

8a310f2

Hide context menu on mobile

3ff53eb

blazejkustra added 2 commits March 28, 2025 18:02

Fix out animation

c552936

Fix lint again

6e530c8

Fix lint again

01706c5

mountiny assigned blazejkustra Mar 28, 2025

mountiny self-requested a review March 28, 2025 23:12

ZhenjaHorbach approved these changes Mar 29, 2025

View reviewed changes

[UX Reliability] Use new modal in BaseReportActionContextMenu #56606

Are you sure you want to change the base?

[UX Reliability] Use new modal in BaseReportActionContextMenu #56606

Conversation

BartoszGrajdek commented Feb 10, 2025 • edited Loading

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Mar 4, 2025

blazejkustra commented Mar 4, 2025

shawnborton commented Mar 4, 2025

ZhenjaHorbach commented Mar 4, 2025 • edited Loading

Reviewer Checklist

Screenshots/Videos

ZhenjaHorbach commented Mar 4, 2025

ZhenjaHorbach commented Mar 4, 2025

ZhenjaHorbach commented Mar 4, 2025 • edited Loading

blazejkustra commented Mar 5, 2025

shawnborton commented Mar 25, 2025

ZhenjaHorbach commented Mar 25, 2025

blazejkustra commented Mar 28, 2025

blazejkustra commented Mar 28, 2025

ZhenjaHorbach commented Mar 28, 2025

blazejkustra commented Mar 28, 2025

blazejkustra commented Mar 28, 2025 • edited Loading

ZhenjaHorbach commented Mar 28, 2025 • edited Loading

ZhenjaHorbach commented Mar 28, 2025

blazejkustra commented Mar 28, 2025

ZhenjaHorbach commented Mar 28, 2025 • edited Loading

ZhenjaHorbach commented Mar 28, 2025 • edited Loading

blazejkustra commented Mar 28, 2025

blazejkustra commented Mar 28, 2025

ZhenjaHorbach commented Mar 28, 2025 • edited Loading

blazejkustra commented Mar 28, 2025

ZhenjaHorbach commented Mar 28, 2025

ZhenjaHorbach commented Mar 28, 2025

github-actions bot commented Mar 28, 2025

github-actions bot commented Mar 28, 2025

ZhenjaHorbach commented Mar 29, 2025

ZhenjaHorbach commented Mar 29, 2025

mountiny commented Mar 30, 2025

blazejkustra commented Mar 31, 2025

mountiny commented Mar 31, 2025

ZhenjaHorbach commented Mar 31, 2025 • edited Loading

blazejkustra commented Mar 31, 2025

ZhenjaHorbach commented Mar 31, 2025 • edited Loading

blazejkustra commented Mar 31, 2025

blazejkustra commented Mar 31, 2025

ZhenjaHorbach commented Mar 31, 2025 • edited Loading

ZhenjaHorbach commented Mar 31, 2025 • edited Loading

[UX Reliability] Use new modal in `BaseReportActionContextMenu` #56606

[UX Reliability] Use new modal in `BaseReportActionContextMenu` #56606

BartoszGrajdek commented Feb 10, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 4, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 4, 2025 •

edited

Loading

blazejkustra commented Mar 28, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 28, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 28, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 28, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 28, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 31, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 31, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 31, 2025 •

edited

Loading

ZhenjaHorbach commented Mar 31, 2025 •

edited

Loading