bump react-native-onyx to 3.0.7 by TMisiukiewicz · Pull Request #73283 · Expensify/App

TMisiukiewicz · 2025-10-23T06:23:20Z

Explanation of Change

Fixed Issues

$ #72679
PROPOSAL:

Tests

Open console
Run the following code in the console:

Onyx.setCollection("transactionViolations_", {
    "transactionViolations_1": [
        {
            "data": {
                "duplicates": [
                    "4912810523916020917",
                    "5084191451238257041",
                    "8264628833372117303"
                ],
                "tooltip": "List the potential duplicate transactions and merge, delete, or ignore them."
            },
            "name": "duplicatedTransaction",
            "showInReview": true,
            "type": "warning"
        }
    ],
    "transactionViolations_2": null,
    "transactionViolations_3": null,
    "transactionViolations_4": null,
    "transactionViolations_5": null,
    "transactionViolations_6": null,
});

Verify the log [info] [OnyxDerived] dependency transactionViolations_ for derived key reportAttributes changed, recomputing - "" is displayed only once

Verify that no errors appear in the JS console

Offline tests

QA Steps

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

Open the app
Background the app for a longer period of time
Go back to the app
Verify you are able to navigate through the app

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

ios.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

github-actions · 2025-10-23T06:23:34Z

⚠️ 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. ⚠️

github-actions · 2025-10-23T06:42:53Z

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

This reverts commit bbc7cb1.

melvin-bot · 2025-10-23T07:25:52Z

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

github-actions · 2025-10-23T08:10:34Z

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

github-actions · 2025-10-23T08:26:04Z

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

Android 🤖	iOS 🍎
❌ FAILED ❌	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/73283/index.html
The QR code can't be generated, because the Android build failed

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/73283/NewExpensify.dmg	https://73283.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

dukenv0307 · 2025-10-23T08:46:03Z

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

Screen.Recording.2025-10-23.at.15.44.19.mov

Android: mWeb Chrome

Screen.Recording.2025-10-23.at.15.40.18.mov

iOS: HybridApp

Screen.Recording.2025-10-23.at.15.43.32.mov

iOS: mWeb Safari

Screen.Recording.2025-10-23.at.15.39.43.mov

MacOS: Chrome / Safari

Screen.Recording.2025-10-23.at.15.35.17.mov

MacOS: Desktop

Screen.Recording.2025-10-23.at.15.45.18.mov

dukenv0307 · 2025-10-23T08:49:26Z

@mountiny The PR looks good, [OnyxDerived] dependency appears once and I also don't face the hang issue. Can you please ask QA team to test again?

mountiny

@JS00001 are you waiting on anything or can we merge?

OSBotify · 2025-10-23T12:33:25Z

✋ 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 · 2025-10-23T13:12:02Z

🚀 Deployed to staging by https://github.com/JS00001 in version: 9.2.37-1 🚀

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

nlemma · 2025-10-24T15:01:32Z

@TMisiukiewicz when you mentioned "Background the app for a longer period of time" how long exactly do you mean?

OSBotify · 2025-10-24T17:54:13Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.2.37-8 🚀

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

TMisiukiewicz · 2025-10-28T08:20:53Z

@nlemma I'm not sure when full reconnect happens, but I think it should be at least an hour or something. Most of the reports about performance issues we get are coming from scenario where people are back to the app next day

bump onyx 3.0.7

90fcdc7

melvin-bot Bot assigned TMisiukiewicz Oct 23, 2025

temporary: add full reconnect button

bbc7cb1

This comment has been minimized.

Sign in to view

Revert "temporary: add full reconnect button"

1ae4542

This reverts commit bbc7cb1.

TMisiukiewicz marked this pull request as ready for review October 23, 2025 07:25

TMisiukiewicz requested a review from a team as a code owner October 23, 2025 07:25

melvin-bot Bot requested review from dukenv0307 and removed request for a team October 23, 2025 07:25

dukenv0307 approved these changes Oct 23, 2025

View reviewed changes

melvin-bot Bot requested a review from JS00001 October 23, 2025 08:46

JS00001 approved these changes Oct 23, 2025

View reviewed changes

mountiny approved these changes Oct 23, 2025

View reviewed changes

JS00001 merged commit 56b2010 into Expensify:main Oct 23, 2025
35 checks passed

OSBotify mentioned this pull request Oct 23, 2025

Deploy Checklist: New Expensify 2025-10-23 #73307

Closed

88 tasks

Conversation

TMisiukiewicz commented Oct 23, 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!

github-actions Bot commented Oct 23, 2025

Uh oh!

github-actions Bot commented Oct 23, 2025

Uh oh!

This comment has been minimized.

melvin-bot Bot commented Oct 23, 2025

Uh oh!

github-actions Bot commented Oct 23, 2025

Uh oh!

github-actions Bot commented Oct 23, 2025

Uh oh!

dukenv0307 commented Oct 23, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

dukenv0307 commented Oct 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Oct 23, 2025

Uh oh!

OSBotify commented Oct 23, 2025

Uh oh!

nlemma commented Oct 24, 2025

Uh oh!

OSBotify commented Oct 24, 2025

Uh oh!

TMisiukiewicz commented Oct 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

TMisiukiewicz commented Oct 23, 2025 •

edited

Loading

dukenv0307 commented Oct 23, 2025 •

edited

Loading