Menu - The bottom menu flickers on tapping app's back button from overview page #58700

thelullabyy · 2025-03-19T11:05:52Z

Explanation of Change

Fixed Issues

$#57279
PROPOSAL:#57279 (comment)

Tests

Launch app
Go to workspace settings
Tap overview/ members/ categories
Tap app's back button
Verify: The bottom menu inbox/reports/settings not flicker on tapping app's back button from overview/ members/ categories page

Verify that no errors appear in the JS console

Offline tests

QA Steps

Launch app
Go to workspace settings
Tap overview/ members/ categories
Tap app's back button
Verify: The bottom menu inbox/reports/settings not flicker on tapping app's back button from overview/ members/ categories page

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android_native.mov

Android: mWeb Chrome

android_chorme.mov

iOS: Native

ios_native.mp4

iOS: mWeb Safari

ios_safari.mp4

MacOS: Chrome / Safari

chorme.mov

MacOS: Desktop

desktop.mov

…iew page

shawnborton · 2025-03-19T22:18:28Z

Video looks good to me, but cc @mountiny in case we want to have the agency that implemented this take a quick looksie just to make sure it checks out.

mountiny · 2025-03-19T22:40:08Z

good shout, added them for a review

shawnborton · 2025-03-25T11:50:40Z

What's the latest here? Can we try to keep this one moving along please? Thanks!

mountiny · 2025-03-25T11:56:37Z

Huh seems like Pullerbear is stuck on this one, adding @rlinoz and @Ollyws as reviewers from the linked issue

mountiny · 2025-03-25T11:57:03Z

@Ollyws Can you please jump on the review?

github-actions · 2025-03-25T11:57:33Z

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

github-actions · 2025-03-25T12:05:27Z

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

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
Android Hybrid 🤖🔄	iOS Hybrid 🍎🔄
❌ FAILED ❌	❌ FAILED ❌
The QR code can't be generated, because the Android Hybrid build failed	The QR code can't be generated, because the iOS Hybrid build failed
Desktop 💻	Web 🕸️
❌ FAILED ❌	https://58700.pr-testing.expensify.com
The QR code can't be generated, because the Desktop build failed

👀 View the workflow run that generated this build 👀

adamgrzybowski · 2025-03-25T12:10:03Z

Makes sense to me! 🚀

Ollyws · 2025-03-25T17:57:29Z

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

01_Android_Native.mp4

Android: mWeb Chrome

02_Android_Chrome.mp4

iOS: Native

03_iOS_Native.mp4

iOS: mWeb Safari

04_iOS_Safari.mp4

MacOS: Chrome / Safari

05_MacOS_Chrome.mp4

MacOS: Desktop

06_MacOS_Desktop.mp4

Ollyws

LGTM.

OSBotify · 2025-03-25T18:19:04Z

✋ 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 · 2025-03-26T06:13:36Z

🚀 Deployed to staging by https://github.com/rlinoz in version: 9.1.19-0 🚀

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

github-actions · 2025-03-27T13:30:45Z

🚀 Deployed to production by https://github.com/cristipaval in version: 9.1.19-5 🚀

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

fix: The bottom menu flickers on tapping app's back button from overv…

892291c

…iew page

thelullabyy marked this pull request as ready for review March 19, 2025 11:15

thelullabyy requested review from a team as code owners March 19, 2025 11:15

fix: replace height by pointerEvents

b47279c

mountiny assigned thelullabyy Mar 19, 2025

mountiny requested review from WojtekBoman and adamgrzybowski March 19, 2025 22:40

mountiny requested review from rlinoz and Ollyws March 25, 2025 11:56

WojtekBoman approved these changes Mar 25, 2025

View reviewed changes

Ollyws approved these changes Mar 25, 2025

View reviewed changes

rlinoz approved these changes Mar 25, 2025

View reviewed changes

rlinoz merged commit cf5c513 into Expensify:main Mar 25, 2025
17 of 18 checks passed

github-actions bot mentioned this pull request Mar 26, 2025

Deploy Checklist: New Expensify 2025-03-26 #59127

Closed

50 tasks

cristipaval mentioned this pull request Mar 26, 2025

[Due for payment 2025-04-16] Modal with payment methods blinks #58705

Closed

8 tasks

melvin-bot bot mentioned this pull request Mar 27, 2025

[Due for payment 2025-04-03] [$250] Android - Menu - The bottom menu flickers on tapping app's back button from overview page #57279

Closed

8 tasks

Ollyws mentioned this pull request Apr 3, 2025

Implement flexible bottom tab bar #49539

Merged

50 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Menu - The bottom menu flickers on tapping app's back button from overview page #58700

Menu - The bottom menu flickers on tapping app's back button from overview page #58700

Uh oh!

thelullabyy commented Mar 19, 2025 •

edited

Loading

Uh oh!

shawnborton commented Mar 19, 2025

Uh oh!

mountiny commented Mar 19, 2025

Uh oh!

shawnborton commented Mar 25, 2025

Uh oh!

mountiny commented Mar 25, 2025

Uh oh!

mountiny commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 25, 2025

Uh oh!

adamgrzybowski commented Mar 25, 2025

Uh oh!

Ollyws commented Mar 25, 2025

Uh oh!

Ollyws left a comment

Uh oh!

Uh oh!

OSBotify commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 26, 2025

Uh oh!

github-actions bot commented Mar 27, 2025

Uh oh!

Uh oh!

Menu - The bottom menu flickers on tapping app's back button from overview page #58700

Menu - The bottom menu flickers on tapping app's back button from overview page #58700

Uh oh!

Conversation

thelullabyy commented Mar 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

shawnborton commented Mar 19, 2025

Uh oh!

mountiny commented Mar 19, 2025

Uh oh!

shawnborton commented Mar 25, 2025

Uh oh!

mountiny commented Mar 25, 2025

Uh oh!

mountiny commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 25, 2025

Uh oh!

adamgrzybowski commented Mar 25, 2025

Uh oh!

Ollyws commented Mar 25, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

Ollyws left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Mar 25, 2025

Uh oh!

github-actions bot commented Mar 26, 2025

Uh oh!

github-actions bot commented Mar 27, 2025

Uh oh!

Uh oh!

thelullabyy commented Mar 19, 2025 •

edited

Loading