Skip to content

[cp staging] Revert "Merge pull request #98611 from thelullabyy/fix-03/90366" - #99675

Merged
JS00001 merged 1 commit into
mainfrom
jsenyitko-big-revert
Aug 27, 2026
Merged

[cp staging] Revert "Merge pull request #98611 from thelullabyy/fix-03/90366"#99675
JS00001 merged 1 commit into
mainfrom
jsenyitko-big-revert

Conversation

@JS00001

@JS00001 JS00001 commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Explanation of Change

This reverts commit a29eb30, reversing changes made to e49e547.

Fixed Issues

$ #99641
$ #99636
$ #99630
$ #99627
$ #99621
$ #99619
$ #99617
$ #99616
$ #99614
$ #99612
$ #99609

Tests

N/A

  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

N/A

  • Verify that no errors appear in the JS console

PR Author Checklist

N/A

  • 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
    • MacOS: Desktop
  • 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.
  • I verified that each 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

Screenshots/Videos

This reverts commit a29eb30, reversing
changes made to e49e547.
@JS00001
JS00001 requested review from a team as code owners August 27, 2026 15:03
@melvin-bot
melvin-bot Bot requested review from joekaufmanexpensify and thelullabyy and removed request for a team August 27, 2026 15:04
@melvin-bot

melvin-bot Bot commented Aug 27, 2026

Copy link
Copy Markdown

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

@melvin-bot
melvin-bot Bot removed the request for review from a team August 27, 2026 15:04
@JS00001 JS00001 changed the title Revert "Merge pull request #98611 from thelullabyy/fix-03/90366" [cp staging] Revert "Merge pull request #98611 from thelullabyy/fix-03/90366" Aug 27, 2026
@codecov

codecov Bot commented Aug 27, 2026

Copy link
Copy Markdown

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/ONYXKEYS.ts 100.00% <ø> (ø)
src/components/MoneyReportHeaderMoreContent.tsx 100.00% <100.00%> (+100.00%) ⬆️
...stReportView/MoneyRequestReportTransactionList.tsx 0.29% <ø> (+<0.01%) ⬆️
src/components/PopoverMenu/index.tsx 92.26% <100.00%> (+1.17%) ⬆️
...archList/ListItem/TransactionGroupListExpanded.tsx 68.18% <ø> (ø)
src/hooks/useNavigateToTransactionThread.ts 44.44% <100.00%> (-34.51%) ⬇️
src/libs/ExportOnyxState/common.ts 80.95% <ø> (ø)
src/pages/home/RecentlyAddedSection/index.tsx 100.00% <ø> (ø)
src/pages/inbox/ReportNavigateAwayHandler.tsx 70.12% <100.00%> (-0.39%) ⬇️
src/components/MoneyRequestHeader.tsx 0.00% <0.00%> (ø)
... and 5 more
... and 12 files with indirect coverage changes

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

Copy link
Copy Markdown

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: bac6c8af8d

ℹ️ 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".

@@ -578,17 +574,6 @@ function Search({

const isTransactionItem = isTransactionListItemType(item);
const backTo = Navigation.getActiveRoute();

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore carousel seeding for flat expense searches

When a user opens a transaction from a flat Spend/Expenses search, onSelectRow now navigates without populating or clearing TRANSACTION_THREAD_NAVIGATION_TRANSACTION_IDS; no other caller seeds the carousel for this branch. Consequently the transaction RHP either has no previous/next navigation or can reuse stale IDs left by another flow, so seed the current ordered transaction IDs before opening the result.

Useful? React with 👍 / 👎.

Comment on lines 61 to +64
const prevNextTransactionsSelector = useCallback(
(allTransactions: OnyxCollection<OnyxTypes.Transaction>) =>
[currentTransactionID, prevTransactionID, nextTransactionID].map((transactionID) => {
const key = `${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}` as const;
return allTransactions?.[key] ?? snapshot?.data?.[key];
}),
[currentTransactionID, nextTransactionID, prevTransactionID, snapshot],
[currentTransactionID, prevTransactionID, nextTransactionID].map((transactionID) => allTransactions?.[`${ONYXKEYS.COLLECTION.TRANSACTION}${transactionID}`]),
[currentTransactionID, nextTransactionID, prevTransactionID],

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Retain snapshot data for grouped-search carousel siblings

When an expense is opened from a grouped search while its siblings exist only in the search snapshot—such as offline or before OpenReport hydrates them—this selector returns undefined for those sibling IDs. The buttons are still rendered from the saved ID list, but pressing one cannot resolve its transaction, parent action, or report and ultimately calls Navigation.setParams with an undefined reportID; preserve the originating snapshot and use it as the fallback for carousel resolution.

Useful? React with 👍 / 👎.

Comment on lines 118 to 122
const focusedRoute = findFocusedRoute(navigationRef.getRootState());
if (focusedRoute?.name && (CAROUSEL_PRESERVING_SCREENS as readonly string[]).includes(focusedRoute.name)) {
if (focusedRoute?.name === SCREENS.RIGHT_MODAL.SEARCH_REPORT || focusedRoute?.name === SCREENS.TRANSACTION_DUPLICATE.DYNAMIC_REVIEW) {
return;
}
clearActiveTransactionIDs();

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Preserve carousel state while opening the parent report

When the transaction subtitle pushes its parent onto SEARCH_MONEY_REQUEST_REPORT or EXPENSE_REPORT, this transaction-navigation component unmounts while one of those routes is focused. Because they are no longer included in this guard, cleanup clears the active IDs; returning to the underlying expense then loses its counter and previous/next buttons. Treat those parent-report RHP routes as carousel-preserving screens.

Useful? React with 👍 / 👎.

@JS00001
JS00001 merged commit 9ab8216 into main Aug 27, 2026
47 of 48 checks passed
@JS00001
JS00001 deleted the jsenyitko-big-revert branch August 27, 2026 15:15
@github-actions

Copy link
Copy Markdown
Contributor

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

OSBotify pushed a commit that referenced this pull request Aug 27, 2026
[cp staging] Revert "Merge pull request #98611 from thelullabyy/fix-03/90366"

(cherry picked from commit 9ab8216)

(cherry-picked to staging by AndrewGable)
@OSBotify OSBotify added the CP Staging marks PRs that have been CP'd to staging label Aug 27, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 9.4.62-4 🚀

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

@os-botify

os-botify Bot commented Aug 27, 2026

Copy link
Copy Markdown

🔁 Filed a Staging retest request for deploy blockers #99641, #99636, #99630, #99627, #99621, #99619, #99617, #99616, #99614, #99612, #99609 after this PR was cherry-picked to staging.

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 No help site changes required.

This PR reverts #98611 (issue #90366), which was a purely visual/UX standardization of the expense report and expense headers — carousel counter (X of X / currentOfTotal) styling, consistent next/previous button placement, and always showing the carousel when opening an expense from the Spend page. It touches header components, navigation helpers, and the currentOfTotal translation string.

None of this is documented at that level of detail in docs/articles, so reverting it doesn't invalidate any help content.

Why no article needs updating
  • The help site documents what users can do (view, filter, manage expenses/reports), not the exact placement of carousel counter buttons or the X of X label on headers.
  • The only "Carousel navigation" mention is in Getting-Started-with-the-Spend-Page.md, under Report Previews — that refers to the report-preview carousel in the Inbox, a different UI element from the header carousel counter this PR reverts. It remains accurate.
  • Reverts restore previously shipping behavior, so existing docs already reflect the post-revert state.

Since no changes are needed, I did not open a docs PR.


view run

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.4.62-4 🚀

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

Bundle Size Analysis (Sentry):

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 9.4.63-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

🤖 No help site changes required.

This PR reverts #98611 (issue #90366), which was a purely visual/UX standardization of the expense report and expense headers — carousel counter (X of X / currentOfTotal) styling, consistent next/previous button placement, and always showing the carousel when opening an expense from the Spend page. It touches header components, navigation helpers, and the currentOfTotal translation string.

None of this is documented at that level of detail in docs/articles, so reverting it doesn't invalidate any help content.

Why no article needs updating
  • The help site documents what users can do (view, filter, manage expenses/reports), not the exact placement of carousel counter buttons or the X of X label on headers.
  • The only "Carousel navigation" mention is in Getting-Started-with-the-Spend-Page.md, under Report Previews — that refers to the report-preview carousel in the Inbox, a different UI element from the header carousel counter this PR reverts. It remains accurate.
  • Reverts restore previously shipping behavior, so existing docs already reflect the post-revert state.

Since no changes are needed, I did not open a docs PR.


view run

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

Labels

CP Staging marks PRs that have been CP'd to staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants