Skip to content

Onyx bump to v3.0.61#85919

Merged
mountiny merged 20 commits intoExpensify:mainfrom
callstack-internal:VickyStash/refactor/82871-bump-onyx-3.0.46
Apr 21, 2026
Merged

Onyx bump to v3.0.61#85919
mountiny merged 20 commits intoExpensify:mainfrom
callstack-internal:VickyStash/refactor/82871-bump-onyx-3.0.46

Conversation

@VickyStash
Copy link
Copy Markdown
Contributor

@VickyStash VickyStash commented Mar 20, 2026

Explanation of Change

This is the second apply of the same Onyx updates.

Previous bump: #85248
Bump revert: #85767
Onyx revert: Expensify/react-native-onyx#758
New Onyx PR: Expensify/react-native-onyx#760

It was reverted cause after merging another PR: #84622, several issues have appeared.
But they were not caused by the Onyx bump on their own (for more context check this slack thread - link).

Just to be safe, I'll include previously linked blockers to the test steps.


Bumps react-native-onyx to 3.0.61.

This Onyx update changes subscriber notifications to be more synchronous, which exposed two issues in the App:

  1. Side effect in render bodyupdateLastAccessedWorkspace() was called directly during render in the withPolicy HOC, causing "Cannot update a component while rendering a different component" errors. Wrapped in useEffect. (context)

  2. New expense scroll/highlight race condition — Faster Onyx updates caused useNewTransactions to fire before navigation completed, so isFocused was still false and new transactions were missed. Moved the focus check into the scroll setTimeout callback via a ref, so it evaluates at scroll time rather than render time. (context)

Fixed Issues

$ #82871
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console

The E/App should work the same way as before. Let's verify basic test steps:

  1. Login with a account.
  2. Navigate to a chat, send a message. React to that message.
  3. Reply to that message in a new thread.
  4. Create a new task, navigate to its details and mark it as completed.
  5. Create a couple of new expenses for someone else, and make sure they are correctly highlighted. Navigate to its details.
  6. Go to Reports tab, Expenses, make sure you can find your expenses and see its details.
  7. Create a new workspace, make sure the rooms were created, and no new warnings appear in the console.
  8. Add a member to the workspace. See it works the same way as before.

#85755

  1. Go to any 1:1 chat
  2. Click + > Create expense
  3. Click "Choose files" and select receipt from computer
  4. Click "Create expense"
  5. Expense is created from receipt image from computer

#85669

  1. Create workspace
  2. Go to workspace chat and submit manual expense with receipt> Complete the process
  3. Receipt should be displayed in the expense

Offline tests

Same, as in the Tests section

QA Steps

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

  • Verify that no errors appear in the JS console

Same, as in the Tests section

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 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.mp4
Android: mWeb Chrome
android_web.mp4
iOS: Native
ios.mov
iOS: mWeb Safari
ios_web.mov
MacOS: Chrome / Safari
web.mp4

…owgrade-onyx-to-v3.0.45"

This reverts commit 5277b58, reversing
changes made to 7933470.
@github-actions
Copy link
Copy Markdown
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. ⚠️

@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 20, 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 Δ
...portActionItem/MoneyRequestReportPreview/index.tsx 90.32% <100.00%> (ø)
src/pages/workspace/withPolicy.tsx 100.00% <100.00%> (ø)
...ReportPreview/MoneyRequestReportPreviewContent.tsx 62.10% <46.15%> (-0.59%) ⬇️
... and 19 files with indirect coverage changes

@VickyStash VickyStash marked this pull request as ready for review March 20, 2026 11:22
@VickyStash VickyStash requested review from a team as code owners March 20, 2026 11:22
@melvin-bot melvin-bot Bot requested review from Krishna2323 and joekaufmanexpensify and removed request for a team March 20, 2026 11:22
@melvin-bot
Copy link
Copy Markdown

melvin-bot Bot commented Mar 20, 2026

@Krishna2323 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 March 20, 2026 11:22
@VickyStash
Copy link
Copy Markdown
Contributor Author

Same reassure test is failing in other PRs too: https://expensify.slack.com/archives/C01GTK53T8Q/p1774001704205909

Copy link
Copy Markdown

@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: 0469bf478b

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

const isFocused = useIsFocused();
// We only want to highlight the new expenses if the screen is focused.
const newTransactionIDs = isFocused ? new Set(newTransactions.map((transaction) => transaction.transactionID)) : undefined;
const newTransactionIDs = new Set(newTransactions.map((transaction) => transaction.transactionID));
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 Gate new transaction highlighting by screen focus

newTransactionIDs is now created unconditionally, so TransactionPreview receives shouldHighlight=true even when the report screen is blurred but still mounted in the navigation stack. In that state the highlight animation can run off-screen and finish before the user returns, which means users can miss the “new expense” highlight entirely; this also contradicts the surrounding intent comment about only highlighting when focused. Keep the new scroll-timing fix, but reintroduce focus-gating for highlight IDs passed to preview items.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

In that state the highlight animation can run off-screen and finish before the user returns, which means users can miss the “new expense” highlight entirely

This is also mentioned in the Test steps (step 5), it highlights correctly on all of the platforms

Comment thread src/components/ReportActionItem/MoneyRequestReportPreview/index.tsx Outdated
@joekaufmanexpensify
Copy link
Copy Markdown
Contributor

No product review needed

@joekaufmanexpensify joekaufmanexpensify removed their request for review March 20, 2026 19:50
@VickyStash VickyStash changed the title Reapply Onyx bump to v3.0.46 [HOLD] Reapply Onyx bump to v3.0.46 Mar 23, 2026
@VickyStash VickyStash marked this pull request as draft March 23, 2026 06:49
@VickyStash
Copy link
Copy Markdown
Contributor Author

Onyx PR was reverted: Expensify/react-native-onyx#758

@VickyStash VickyStash changed the title [HOLD] Reapply Onyx bump to v3.0.46 [HOLD] Reapply Onyx bump to v3.0.x Mar 23, 2026
# Conflicts:
#	package-lock.json
#	package.json
@VickyStash VickyStash dismissed stale reviews from mountiny and Julesssss via 3d33800 April 17, 2026 06:30
@Krishna2323
Copy link
Copy Markdown
Contributor

Reviewing...

@Krishna2323
Copy link
Copy Markdown
Contributor

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
    • 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 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_hybrid.mp4
Android: mWeb Chrome
android_mWeb.mp4
iOS: HybridApp
ios_hybrid.mp4
iOS: mWeb Safari
ios_mweb.mp4
MacOS: Chrome / Safari
web_chrome_2.mp4
web_chrome_3.mp4
web_chrome.mp4

Copy link
Copy Markdown
Contributor

@Krishna2323 Krishna2323 left a comment

Choose a reason for hiding this comment

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

LGTM!

@melvin-bot melvin-bot Bot requested a review from mountiny April 17, 2026 09:12
roryabraham
roryabraham previously approved these changes Apr 17, 2026
@mountiny mountiny changed the title Onyx bump to v3.0.61 [HOLD https://github.com/Expensify/App/pull/87836 in staging] Onyx bump to v3.0.61 Apr 17, 2026
Julesssss
Julesssss previously approved these changes Apr 17, 2026
Copy link
Copy Markdown
Contributor

@Julesssss Julesssss left a comment

Choose a reason for hiding this comment

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

Not merging until this checklist is deployed: #88022

mountiny
mountiny previously approved these changes Apr 19, 2026
Copy link
Copy Markdown
Contributor

@mountiny mountiny left a comment

Choose a reason for hiding this comment

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

LGTM, just consider the suggestion from Rory please

@VickyStash VickyStash dismissed stale reviews from mountiny, Julesssss, and roryabraham via 37bb95f April 20, 2026 07:49
@Julesssss
Copy link
Copy Markdown
Contributor

Checklist getting closer...

@mountiny mountiny changed the title [HOLD https://github.com/Expensify/App/pull/87836 in staging] Onyx bump to v3.0.61 Onyx bump to v3.0.61 Apr 21, 2026
@mountiny
Copy link
Copy Markdown
Contributor

Just deployed so going to merge!

@mountiny mountiny merged commit 4d41d2e into Expensify:main Apr 21, 2026
47 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

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

@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

🚀 Deployed to staging by https://github.com/mountiny in version: 9.3.62-0 🚀

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

Bundle Size Analysis (Sentry):

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants