[HOLD https://github.com/Expensify/App/pull/96853 hit staging][Split #94595] Final PR - Remove useOnyx dependencies arg and bump Onyx

[fabioh8010]

Explanation of Change

• Bumps react-native-onyx to to 3.0.95:
  • Classify "Failed to write blobs" IDB errors as INVALID_DATA (never retry) react-native-onyx#814
  • Remove dependencies argument from useOnyx react-native-onyx#800
• Removes the dependencies parameter (and the DependencyList import) from the App useOnyx wrapper in src/hooks/useOnyx.ts — it was already never forwarded.
• Migrates the last two call sites that still passed the argument, keeping each selector reference stable (React Compiler memoizes the inline/factory selector; both files compile under Babel + OXC):
  • src/components/ReportActionItem/MoneyRequestReportPreview/useReportPreviewActionDecision.ts
  • src/hooks/useReportTransactionViolations.ts
• Deletes the temporary rulesdir/no-useOnyx-dependencies-arg ESLint rule, its config entry, and its seatbelt rows — the 2-argument TypeScript signature now enforces this at compile time, so the lint guard is redundant.

Fixed Issues

$ #95582
$ #94595
$ #97050
PROPOSAL:

Tests

For Expensify/react-native-onyx#814:

No tests needed as #96940 implements a FE protection already.

For Expensify/react-native-onyx#800 (Web / Mobile):

1. Login with an account with Workspace.
2. Create a new expense report, add an expense without Category.
3. Wait a bit, assert the expense is flagged as missing Category.
4. Submit the report, approve it, assert the process works.
5. Fill the missing Category, assert the violation is gone.
6. Mark the report as paid, assert the process works.

• Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as Tests.

• Verify that no errors appear in the JS console

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 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 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)
• 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)
• 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.
• 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

For Expensify/react-native-onyx#800:

Screen.Recording.2026-08-07.at.21.48.45.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

For Expensify/react-native-onyx#800:

Screen.Recording.2026-08-07.at.20.27.06.mov

[github-actions]

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

[fabioh8010]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 07eab47557

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

[fabioh8010]

PR is on hold until #96853 hit staging.

[melvin-bot]

@hoangzinh @nyomanjyotisa One of you needs to 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]

[fabioh8010]

I'm heading to vacations next week and will return on August 17th, someone will take this over from me.

[trjExpensify]

PR doesn’t need product input as a refactor PR. Unassigning and unsubscribing myself.