Remove cache eviction system

[fabioh8010]

Details

This PR is a follow-up of #752. As discussed here, we decided to keep these changes in this separate PR.

Before Onyx had two separate eviction systems sharing infrastructure:

1. Cache eviction — trimmed the in-memory storageMap when maxCachedKeysCount was exceeded, triggered every time a subscriber connected to an evictable key via addKeyToRecentlyAccessedIfNeeded → removeLeastRecentlyUsedKeys. Used recentKeys (LRU of all accessed keys) and maxRecentKeysSize.

2. Storage eviction — freed device storage on capacity errors (quota exceeded, disk full) by evicting the least recently accessed evictable key via retryOperation → getKeyForEviction. Used recentlyAccessedKeys (LRU of evictable keys only) and evictionBlocklist (controlled by useOnyx's canEvict option).

This PR removes cache eviction (1) entirely and simplifies storage eviction (2) by removing the canEvict/blocklist mechanism, while keeping the core storage eviction flow intact. We are also fixing this issue reported some time ago by @VickyStash with this small commit.

In my investigations about storage errors, there were only 895 cases where we could possibly hit the canEvict/blocklist mechanism out of 3364645 errors analysed during a span of 30 days, representing only 0.027% of the cases. Because of this it's reasonable to remove this part and simplify further useOnyx and Onyx internals code.

Related Issues

$ Expensify/App#85252

E/App PR: Expensify/App#86736

Automated Tests

Tests related to cache eviction were removed and new ones were added/changed for storage eviction.

Manual Tests

We don't have much to test here since we are basically removing "dead code", so let's do a basic storage write test in a heavy account. Use Expensify/App#86736 for testing:

1. Login with a heavy account.
2. Click FAB -> Start chat.
3. Search for a email and open a chat.
4. Send a message, assert it works.
5. React to that message, assert it works.

Author Checklist

• I linked the correct issue in the ### Related 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 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 / Chrome
  • iOS / native
  • iOS / 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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 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.js 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 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
  • If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
  • 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 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 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 author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Screen.Recording.2026-04-10.at.09.29.57-compressed.mov

Android: mWeb Chrome

N/A

iOS: Native

Screen.Recording.2026-04-10.at.09.35.08-compressed.mov

iOS: mWeb Safari

Screen.Recording.2026-04-10.at.09.38.19-compressed.mov

MacOS: Chrome / Safari

Screen.Recording.2026-04-10.at.09.42.54-compressed.mov

Screen.Recording.2026-04-10.at.09.45.10-compressed.mov

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 577832e3eb

ℹ️ 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]

@Julesssss I made this change because of this comment from Codex. I tried to remove this then but it make some tests fails and generally I don't think it's safe to push with this PR. I would like to explore this in a follow-up if you don't mind.

[Julesssss]

Fine with me 👍

[mountiny]

Thank you!

[os-botify]

🚀 Published to npm in 3.0.63 🎉