Remove console and record troubleshoot data features by roryabraham · Pull Request #82350 · Expensify/App

roryabraham · 2026-02-13T04:34:15Z

Explanation of Change

Removing the console page and record troubleshoot data feature as they're no longer used or needed. Slack threads:

Also created https://github.com/Expensify/Mobile-Expensify/pull/13850 for removing react-native-release-profiler.

Fixed Issues

related to https://github.com/Expensify/Expensify/issues/594140

Tests

Go to Settings -> Troubleshoot.
Verify you don't see a Console option.
Verify you don't see a Record Troubleshoot Data option.

Verify that no errors appear in the JS console

Offline tests

None.

QA Steps

Same as tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Co-authored-by: Cursor <cursoragent@cursor.com>

…n config Co-authored-by: Cursor <cursoragent@cursor.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

…nCompleteRecording Co-authored-by: Cursor <cursoragent@cursor.com>

melvin-bot · 2026-02-13T04:34:50Z

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

…tive handlers, add sentryLabel, remove unused waitForNavigate Co-authored-by: Cursor <cursoragent@cursor.com>

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ddbdf9e92c

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

roryabraham · 2026-02-13T04:47:37Z

@codex review

codecov · 2026-02-13T04:50:09Z

Codecov Report

❌ Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
...c/pages/settings/Troubleshoot/TroubleshootPage.tsx	0.00%	1 Missing ⚠️

Files with missing lines	Coverage Δ
src/CONST/index.ts	`87.39% <ø> (ø)`
src/ONYXKEYS.ts	`100.00% <ø> (ø)`
src/ROUTES.ts	`12.86% <ø> (+0.12%)`	⬆️
src/SCREENS.ts	`100.00% <ø> (ø)`
src/components/TestToolsModalPage.tsx	`0.00% <ø> (ø)`
src/hooks/useSearchSelector.base.ts	`21.31% <ø> (ø)`
src/libs/Log.ts	`77.27% <100.00%> (-0.91%)`	⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx	`7.53% <ø> (-0.10%)`	⬇️
src/libs/Navigation/AppNavigator/PublicScreens.tsx	`100.00% <ø> (ø)`
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts	`100.00% <ø> (ø)`
... and 3 more

... and 14 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

chatgpt-codex-connector · 2026-02-13T04:56:01Z

Codex Review: Didn't find any major issues. Can't wait for the next one!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

situchan · 2026-02-13T07:47:05Z

If requires C+ testing, I can help

Delete the entire RecordTroubleshootDataToolMenu/ directory (15 files) and remove its import/usage from TroubleshootPage and TestToolsModalPage. Both pages still render TestToolMenu and other debug tools. Co-authored-by: Cursor <cursoragent@cursor.com>

Delete Troubleshoot.ts (recording orchestration) and ProfilingTool.ts (profiling toggle), which were exclusively consumed by the removed RecordTroubleshootDataToolMenu component. Remove shouldShowProfileTool from TestTool.ts along with its now-unused Browser imports. Remove three Onyx keys: APP_PROFILING_IN_PROGRESS, SHOULD_RECORD_TROUBLESHOOT_DATA, and TROUBLESHOOT_RECORDING_START_TIME. Co-authored-by: Cursor <cursoragent@cursor.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

…er dependencies These three packages were exclusively used by the removed RecordTroubleshootDataToolMenu and Troubleshoot action modules. Co-authored-by: Cursor <cursoragent@cursor.com>

chatgpt-codex-connector · 2026-02-13T08:54:54Z

Codex Review: Didn't find any major issues. What shall we delve into next?

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

roryabraham · 2026-02-13T09:16:47Z

I'll leave it up to @Julesssss and @rlinoz if they want C+ testing or not. Given that this is just removing a bunch of code, I'm not sure it's needed here.

Delete the upload_dsyms and upload_dsyms_hybrid fastlane lanes that uploaded dSYM files to Firebase Crashlytics. Sentry handles debug symbol uploads via its own Xcode build phase and Gradle plugin. Also remove the "Upload DSYMs to Firebase for HybridApp" step from deploy.yml that called the now-deleted lane. Co-authored-by: Cursor <cursoragent@cursor.com>

…ipts The release profiler was only used by the now-removed Record Troubleshoot Data feature. This removes: - react-native-release-profiler dependency - scripts/release-profile.ts (local symbolication helper) - scripts/symbolicate-profile.ts (remote artifact download + symbolication) - npm scripts: symbolicate-release:{ios,android,web}, symbolicate-profile Co-authored-by: Cursor <cursoragent@cursor.com>

rlinoz

Always good to remove so many lines 😌

I just have 1 question.

JmillsExpensify

No issues removing these from the product.

- Revert "Remove Firebase Crashlytics dSYM upload lanes and deploy step" since Crashlytics hasn't been fully removed yet - Remove SEARCH_CONTEXT_SHARE_LOG constant and its case in useSearchSelector (ShareLogList was deleted in this PR) Co-authored-by: Cursor <cursoragent@cursor.com>

rlinoz · 2026-02-16T11:55:51Z

all yours @Julesssss

Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # src/pages/settings/AboutPage/ShareLogList/BaseShareLogList.tsx

roryabraham · 2026-02-17T16:21:30Z

resolved conflicts

codecov · 2026-02-17T16:31:24Z

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/CONST/index.ts	`87.39% <ø> (ø)`
src/ONYXKEYS.ts	`100.00% <ø> (ø)`
src/ROUTES.ts	`12.86% <ø> (+0.12%)`	⬆️
src/SCREENS.ts	`100.00% <ø> (ø)`
src/components/TestToolsModalPage.tsx	`0.00% <ø> (ø)`
src/hooks/useSearchSelector.base.ts	`21.31% <ø> (ø)`
src/libs/Log.ts	`77.27% <100.00%> (-0.91%)`	⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx	`7.53% <ø> (-0.10%)`	⬇️
src/libs/Navigation/AppNavigator/PublicScreens.tsx	`100.00% <ø> (ø)`
...igation/linkingConfig/RELATIONS/SETTINGS_TO_RHP.ts	`100.00% <ø> (ø)`
... and 3 more
... and 14 files with indirect coverage changes

rlinoz · 2026-02-17T18:52:12Z

r## 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: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
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 there are no new alerts related to the canBeMissing param for useOnyx
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: HybridApp

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

github-actions · 2026-02-17T19:40:41Z

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

OSBotify · 2026-02-17T19:48:37Z

✋ 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 · 2026-02-17T20:05:33Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6215336-37c0003-ac1f4c3e649a2151fc8267c41dbdc2342f02d3ac/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6215336-37c0003-4c5a9ee28c096e04615982551f35aba2d2074f01/index.html

Web 🕸️
https://82350.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-02-18T00:07:34Z

🚀 Deployed to staging by https://github.com/Julesssss in version: 9.3.21-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

OSBotify · 2026-02-18T22:03:08Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.3.21-4 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

roryabraham and others added 10 commits February 12, 2026 18:18

Remove Console entry points from TroubleshootPage and TestToolsModalPage

921a4c2

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console routes and screens from SCREENS, ROUTES, and navigatio…

9480ae4

…n config Co-authored-by: Cursor <cursoragent@cursor.com>

Delete Console and ShareLogList UI components

f8b456a

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console lib and actions

64de2ce

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console types from types/onyx

3abcdaa

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove DEBUG_CONSOLE constants and Console Onyx keys

b115fb7

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console dependencies from Log.ts and Troubleshoot.ts

8d06cb3

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console translation keys from language files

bfb90a9

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove Console/LOGS usage from RecordTroubleshootDataToolMenu

ddbdf9e

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove logs from troubleshoot export and rename onDisableLogging to o…

8dcf74a

…nCompleteRecording Co-authored-by: Cursor <cursoragent@cursor.com>

roryabraham requested a review from rlinoz February 13, 2026 04:34

roryabraham self-assigned this Feb 13, 2026

roryabraham requested review from a team as code owners February 13, 2026 04:34

melvin-bot Bot requested review from JmillsExpensify and Julesssss and removed request for a team February 13, 2026 04:34

roryabraham and others added 2 commits February 12, 2026 20:39

Fix tsc

d160895

Fix lint and TypeScript errors: remove logsWithParsedMessages from na…

d53647d

…tive handlers, add sentryLabel, remove unused waitForNavigate Co-authored-by: Cursor <cursoragent@cursor.com>

chatgpt-codex-connector Bot reviewed Feb 13, 2026

View reviewed changes

Comment thread src/components/RecordTroubleshootDataToolMenu/BaseRecordTroubleshootDataToolMenu.tsx Outdated

roryabraham and others added 4 commits February 12, 2026 23:58

Remove recordTroubleshootData translation key from all locale files

95d42e1

Co-authored-by: Cursor <cursoragent@cursor.com>

Remove jszip, react-native-blob-util, and react-native-release-profil…

b4ebc3f

…er dependencies These three packages were exclusively used by the removed RecordTroubleshootDataToolMenu and Troubleshoot action modules. Co-authored-by: Cursor <cursoragent@cursor.com>

roryabraham changed the title ~~Remove console and record troubleshoot data features~~ [WIP] Remove console and record troubleshoot data features Feb 13, 2026

roryabraham changed the title ~~[WIP] Remove console and record troubleshoot data features~~ Remove console and record troubleshoot data features Feb 13, 2026

adhorodyski reviewed Feb 13, 2026

View reviewed changes

Comment thread contributingGuides/PERFORMANCE.md

roryabraham and others added 2 commits February 13, 2026 01:34

rlinoz requested changes Feb 13, 2026

View reviewed changes

Comment thread .github/workflows/deploy.yml

Comment thread fastlane/Fastfile

Comment thread fastlane/Fastfile

shubham1206agra reviewed Feb 13, 2026

View reviewed changes

Comment thread src/pages/settings/AboutPage/ShareLogList/BaseShareLogList.tsx

JmillsExpensify reviewed Feb 13, 2026

View reviewed changes

roryabraham and others added 2 commits February 13, 2026 11:15

Remove react-native-release-profiler from Pods

a25d77b

roryabraham requested a review from rlinoz February 13, 2026 19:22

rlinoz previously approved these changes Feb 16, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into Rory-RemoveConsolePage

828e66c

Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # src/pages/settings/AboutPage/ShareLogList/BaseShareLogList.tsx

roryabraham dismissed rlinoz’s stale review via 828e66c February 17, 2026 16:20

rlinoz approved these changes Feb 17, 2026

View reviewed changes

Julesssss approved these changes Feb 17, 2026

View reviewed changes

Julesssss merged commit 6215336 into main Feb 17, 2026
43 of 44 checks passed

Julesssss deleted the Rory-RemoveConsolePage branch February 17, 2026 19:40

OSBotify mentioned this pull request Feb 17, 2026

Deploy Checklist: New Expensify 2026-02-17 #82716

Closed

93 tasks done

Conversation

roryabraham commented Feb 13, 2026 • 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 Feb 13, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

roryabraham commented Feb 13, 2026

Uh oh!

codecov Bot commented Feb 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

chatgpt-codex-connector Bot commented Feb 13, 2026

Uh oh!

situchan commented Feb 13, 2026

Uh oh!

chatgpt-codex-connector Bot commented Feb 13, 2026

Uh oh!

roryabraham commented Feb 13, 2026

Uh oh!

Uh oh!

rlinoz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

JmillsExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

rlinoz commented Feb 16, 2026

Uh oh!

roryabraham commented Feb 17, 2026

Uh oh!

codecov Bot commented Feb 17, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

rlinoz commented Feb 17, 2026

Screenshots/Videos

Uh oh!

Uh oh!

github-actions Bot commented Feb 17, 2026

Uh oh!

OSBotify commented Feb 17, 2026

Uh oh!

github-actions Bot commented Feb 17, 2026

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

OSBotify commented Feb 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

8 participants

roryabraham commented Feb 13, 2026 •

edited

Loading

codecov Bot commented Feb 13, 2026 •

edited

Loading

codecov Bot commented Feb 17, 2026 •

edited by github-actions Bot

Loading