Skip to content

Conversation

@adhorodyski
Copy link
Contributor

@adhorodyski adhorodyski commented Jan 27, 2026

@rlinoz @sosek108

Explanation of Change

This PR deprecates the Timing.ts module as well as any performance tracking done with Firebase. It includes a patch removal.

Let's make sure this PR is well tested on an adhoc.

  • cleanup StartupTimer on iOS
  • cleanup StartupTimer on Android
  • cleanup StartupTimer on iOS (Hybrid)
  • cleanup StartupTimer on Android (Hybrid)

Needs https://github.com/Expensify/Mobile-Expensify/pull/13828 to work with Hybrid.

Fixed Issues

$ #80357
PROPOSAL: N/A

MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/13828

Tests

  1. Open up the app.
  2. Navigate to any report.
  3. Send a message.
  4. Navigate to the Reports page.
  5. Navigate into any report from there.
  6. The App should not crash during this whole time.
  7. Open up Network tools, observe no calls to the /SendPerformanceTimings command have been made.

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Same as 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
  • 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 new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • 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

@github-actions
Copy link
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

Copy link
Contributor

@sosek108 sosek108 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall 🚀

Once concern is about size of the PR. maybe we could split this?

@adhorodyski adhorodyski force-pushed the timing-module-deprecate branch from f2737dc to fc5eead Compare January 27, 2026 20:41
@adhorodyski adhorodyski marked this pull request as ready for review January 27, 2026 20:41
@adhorodyski adhorodyski requested review from a team as code owners January 27, 2026 20:41
@melvin-bot melvin-bot bot requested review from Ollyws and heyjennahay and removed request for a team and heyjennahay January 27, 2026 20:41
@melvin-bot
Copy link

melvin-bot bot commented Jan 27, 2026

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

@adhorodyski adhorodyski changed the title [WIP] chore: deprecate timing.ts chore: deprecate timing.ts Jan 27, 2026
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fc5eead167

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 110 to 113
"@react-native-firebase/analytics": "^22.2.1",
"@react-native-firebase/app": "^22.2.1",
"@react-native-firebase/crashlytics": "^22.2.1",
"@react-native-firebase/perf": "^22.2.1",
"@react-native-google-signin/google-signin": "^10.0.1",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore Firebase Performance dependency for iOS startup timer

Removing @react-native-firebase/perf means the Firebase Performance pod is no longer installed (Podfile.lock drops Firebase/Performance), but ios/NewExpensify/RCTStartupTimer.h still imports FirebasePerformance/FIRPerformance.h. iOS builds that include this native module will fail to compile with a missing module error. Either keep the perf dependency/pod or remove/guard the startup timer’s FirebasePerformance usage on iOS.

Useful? React with 👍 / 👎.

@codecov
Copy link

codecov bot commented Jan 27, 2026

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/Expensify.tsx 84.73% <ø> (-0.08%) ⬇️
src/components/LHNOptionsList/OptionRowLHN.tsx 95.71% <ø> (ø)
...ReportPreview/MoneyRequestReportPreviewContent.tsx 60.92% <ø> (+0.20%) ⬆️
...portActionItem/MoneyRequestReportPreview/index.tsx 89.28% <ø> (ø)
src/components/Search/SearchAutocompleteList.tsx 32.49% <ø> (-0.11%) ⬇️
...rc/components/Search/SearchRouter/SearchButton.tsx 100.00% <ø> (ø)
src/components/Search/index.tsx 30.14% <ø> (+0.05%) ⬆️
src/libs/API/types.ts 100.00% <ø> (ø)
src/libs/BootSplash/index.native.ts 100.00% <100.00%> (ø)
src/libs/BootSplash/index.ts 0.00% <ø> (ø)
... and 14 more
... and 9 files with indirect coverage changes

rlinoz
rlinoz previously approved these changes Jan 27, 2026
Copy link
Contributor

@rlinoz rlinoz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, let's just update the doc before merging.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if this is just the setup we need to add the tags we want to Sentry, for the big accounts. So we could just move this file to telemetry and set the attributes there.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we can just write that in another PR anyway.

@adhorodyski adhorodyski changed the title chore: deprecate timing.ts [WIP] chore: deprecate timing.ts Jan 27, 2026
@fabioh8010
Copy link
Contributor

@adhorodyski @rlinoz @sosek108

Updates:

  • Updated both E/App and Mobile-Expensify PRs and fixed CI issues
  • Ran local builds for Web, Standalone and Hybrid, all passed except iOS Standalone with this error (looks like it's unrelated to the changes here and already happening on main though)

The following build commands failed:
CompileAssetCatalogVariant thinned /Users/fabiohenriques/Library/Developer/Xcode/DerivedData/NewExpensify-ghqcewtwqrncwpadxywxtcecpjza/Build/Products/DebugDevelopment-iphonesimulator/New\ Expensify\ Dev.app /Users/fabiohenriques/Documents/Work/Callstack/Projects/Expensify/expensify-app/ios/NewExpensify/Images.xcassets (in target 'NewExpensify' from project 'NewExpensify')
Building workspace NewExpensify with scheme New Expensify Dev and configuration DebugDevelopment
(2 failures)

@fabioh8010
Copy link
Contributor

fabioh8010 commented Jan 28, 2026

Confirmed that iOS Standalone is also failing on main for me -> https://expensify.slack.com/archives/C01GTK53T8Q/p1769596367015779
EDIT: probably just my machine

@github-actions
Copy link
Contributor

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

@github-actions

This comment has been minimized.

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80659 Mobile-Expensify PR Expensify/Mobile-Expensify#13828.

Android 🤖 iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-1e7603d-e2552dea8fdeb3b0c53cdcfbcd2f54c28a6dd4f8/index.html ❌ FAILED ❌
Android The QR code can't be generated, because the iOS build failed
Web 🕸️
https://80659.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

@IuliiaHerets
Copy link

Hi @adhorodyski, this closed issue is reproducible on the ad-hoc build.
It is not reproducible on STG or PROD, as the PR was reverted.
Should we log it specifically for the ad-hoc build?

@adhorodyski
Copy link
Contributor Author

Synced with main, it was already 2d old. Let's rerun the build.

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #80659 Mobile-Expensify PR Expensify/Mobile-Expensify#13828.

Android 🤖 iOS 🍎
❌ FAILED ❌ https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-2ba05299048e335327e88b5d0e980e2a186f5e7a/index.html
The QR code can't be generated, because the Android build failed iOS
Web 🕸️
https://80659.pr-testing.expensify.com
Web

👀 View the workflow run that generated this build 👀

@github-actions
Copy link
Contributor

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

@github-actions
Copy link
Contributor

@rlinoz
Copy link
Contributor

rlinoz commented Jan 30, 2026

@IuliiaHerets can you please use this one? #80659 (comment) I should have the bugs from other issues fixed.

@IuliiaHerets
Copy link

@rlinoz, just to confirm, you’d like to check this issue on the new build?

@IuliiaHerets
Copy link

@rlinoz issue is not repro using the newest build

25.mp4

@rlinoz
Copy link
Contributor

rlinoz commented Jan 30, 2026

@IuliiaHerets yes thank you! and if we could do the rest of the QA in that build, if it didn't get completed in the previous one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants