Fix : Investigate Profiling: iOS - Chrome/Safari and MacOS - Safari by M00rish · Pull Request #58065 · Expensify/App

M00rish · 2025-03-09T17:09:41Z

Explanation of Change

hiding profiling tool in the debugging modal:

safari or Firefox on all platforms
chrome on IOS

Fixed Issues

Tests

1- log in to with any account
2- for mobile/app do a four fingers tap or for desktop/browsers hit CMD + D.
3- verify profiling tool is not shown for :

safari or Firefox on all platforms
for chrome on IOS as well
Verify that no errors appear in the JS console

Offline tests

1- log in to with any account
2- for mobile/app do a four fingers tap or for desktop/browsers hit CMD + D.
3- verify profiling tool is not shown for :

safari or Firefox on all platforms
for chrome on IOS as well

QA Steps

1- log in to with any account
2- for mobile/app do a four fingers tap or for desktop/browsers hit CMD + D.
3- verify profiling tool is not shown for :

safari or Firefox on all platforms
for chrome on IOS as well
Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

Android: mWeb FireFox

iOS: Native

iOS: mWeb Safari

MacOS: Chrome

MacOS: Safari

MacOS: FireFox

MacOS: Desktop

melvin-bot · 2025-03-09T17:09:46Z

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

luacmartins

@M00rish lint is failing. You can fix it by running npm run prettier

M00rish · 2025-03-11T17:39:47Z

Hmm, seems not signed properly. I will check that

suneox · 2025-03-11T17:58:36Z

src/components/TestToolsModal.tsx

    const styles = useThemeStyles();
    const {translate} = useLocalize();

+    const shouldShowProfileTool = () => {


Suggested change

const shouldShowProfileTool = () => {

const shouldShowProfileTool = useMemo(() => {

updated please review again, thanks.

suneox · 2025-03-11T18:08:22Z

Hmm, seems not signed properly. I will check that

We have a guideline for configuring signing commit in this section

https://github.com/suneox/ExpensifyApp/blob/1e82faeffc86012ef0252e9c800ad0d69657a120/contributingGuides/CONTRIBUTING.md?plain=1#L157-L169

suneox · 2025-03-12T03:52:35Z

@M00rish Please follow the contributing guidelines for next time.

Please never force push when a PR review has already started

M00rish · 2025-03-12T04:00:49Z

Yes, last commit was not signed correctly. That's why, in this case, if a commit need to be redone, do I create a new PR?

Anyway this is noted for next time. Thanks

suneox · 2025-03-12T07:23:28Z

Yes, last commit was not signed correctly. That's why, in this case, if a commit need to be redone, do I create a new PR?

Anyway this is noted for next time. Thanks

It's just a note for next time.

suneox · 2025-03-12T07:23:50Z

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

iOS: Native

iOS: mWeb

Safari

ScreenRecording_03-12-2025.00-22-30_1.safari.MP4

Firefox

ScreenRecording_03-12-2025.00-23-28_1.firefox.MP4

Chrome

ScreenRecording_03-12-2025.00-25-30_1.chrome.MP4

Opera

ScreenRecording_03-12-2025.00-24-43_1.opera.MP4

MacOS: Chrome / Opera / Safari

Safari

Screen.Recording.2025-03-12.at.00.27.41.mp4

Opera

Chrome

Screen.Recording.2025-03-12.at.00.26.47.mp4

MacOS: Desktop

Screen.Recording.2025-03-12.at.00.28.36.mp4

suneox · 2025-03-12T14:39:11Z

@M00rish Could you please try to merge with the latest main branch to trigger the pipeline?

luacmartins · 2025-03-12T17:21:09Z

@M00rish Could you please try to merge with the latest main branch to trigger the pipeline?

What do you mean by trigger the pipeline?

luacmartins

LGTM

luacmartins · 2025-03-12T20:04:37Z

@suneox are you still reviewing the PR? Just asking because it seems like you completed the checklist, but there's no approval/change requests.

OSBotify · 2025-03-13T00:24:06Z

✋ 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-14T02:18:25Z

🚀 Deployed to staging by https://github.com/luacmartins in version: 9.1.13-0 🚀

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

github-actions · 2025-03-17T11:40:53Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.13-5 🚀

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

add function to hide profiling tool

8f0cdb0

M00rish requested a review from a team as a code owner March 9, 2025 17:09

melvin-bot bot requested a review from suneox March 9, 2025 17:09

melvin-bot bot removed the request for review from a team March 9, 2025 17:09

M00rish mentioned this pull request Mar 9, 2025

[Due for payment 2025-03-24] [$250] [LOW] Investigate Profiling: iOS - Chrome/Safari and MacOS - Safari #56787

Closed

luacmartins self-requested a review March 10, 2025 16:31

luacmartins reviewed Mar 10, 2025

View reviewed changes

suneox reviewed Mar 11, 2025

View reviewed changes

update according to review and fix lint

d174b20

luacmartins requested review from luacmartins and suneox March 12, 2025 17:21

luacmartins approved these changes Mar 12, 2025

View reviewed changes

suneox approved these changes Mar 13, 2025

View reviewed changes

melvin-bot bot requested a review from luacmartins March 13, 2025 00:07

luacmartins approved these changes Mar 13, 2025

View reviewed changes

luacmartins merged commit 31c531c into Expensify:main Mar 13, 2025
19 checks passed

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

Deploy Checklist: New Expensify 2025-03-14 #58424

Closed

90 tasks

M00rish deleted the hideProfiling-new branch March 16, 2025 01:03

	const shouldShowProfileTool = () => {
	const shouldShowProfileTool = useMemo(() => {

Conversation

M00rish commented Mar 9, 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!

melvin-bot bot commented Mar 9, 2025

Uh oh!

luacmartins left a comment

Choose a reason for hiding this comment

Uh oh!

M00rish commented Mar 11, 2025

Uh oh!

suneox Mar 11, 2025

Choose a reason for hiding this comment

Uh oh!

M00rish Mar 12, 2025

Choose a reason for hiding this comment

Uh oh!

suneox commented Mar 11, 2025

Uh oh!

suneox commented Mar 12, 2025

Uh oh!

M00rish commented Mar 12, 2025

Uh oh!

suneox commented Mar 12, 2025

Uh oh!

suneox commented Mar 12, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

suneox commented Mar 12, 2025

Uh oh!

luacmartins commented Mar 12, 2025

Uh oh!

luacmartins left a comment

Choose a reason for hiding this comment

Uh oh!

luacmartins commented Mar 12, 2025

Uh oh!

Uh oh!

OSBotify commented Mar 13, 2025

Uh oh!

github-actions bot commented Mar 14, 2025

Uh oh!

github-actions bot commented Mar 17, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

M00rish commented Mar 9, 2025 •

edited

Loading