[Onyx bump] Bump react-native-onyx to 3.0.115 by sosek108 · Pull Request #101085 · Expensify/App

sosek108 · 2026-09-14T12:40:55Z

Explanation of Change

Bumps react-native-onyx from 3.0.113 to 3.0.115. The bump contains two Onyx PRs:

fix(storage): degrade to memory-only when IndexedDB is unavailable react-native-onyx#845: On WebKit (every browser on iOS, Chrome included) the indexedDB global is undeclared in private tabs and in Lockdown Mode, so reading it throws ReferenceError: Can't find variable: indexedDB. Onyx never classified that error, never fell back to the in-memory provider, and retried an operation that can never succeed. This adds an UNAVAILABLE error class so Onyx degrades to memory-only storage and skips the retries.
Set cache-mode: read on reusable workflow calls from low-trust triggers react-native-onyx#849: Adds cache-mode: read to the CLA job in the Onyx repo's .github/workflows/cla.yml, which the new cache-call-unrestricted actionlint check requires. It is a workflow-only change with no library code or behavior change.

No E/App source changes, package.json / package-lock.json only.

Fixed Issues

$ #100844
$ https://github.com/Expensify/Expensify/issues/678960
PROPOSAL: N/A (internal fix)

Tests

Onyx #849 is workflow-only and needs no App testing. The steps below cover Onyx #845.

Open the App in iOS Safari or Chrome for iOS in a private tab (or enable Lockdown Mode for the site).
Sign in and navigate around: open a report, send a message, switch chats.
Verify the app works normally (backed by the in-memory provider) instead of failing to load.
Check the console: exactly one degrade log, plus Storage operation skipped retry; the storage engine is unavailable... info logs for writes. No Can't find variable: indexedDB ReferenceError, and no Storage operation failed after N retries alerts.
Repeat in a normal (non-private) tab and verify IndexedDB is still used and nothing degrades.

Verify that no errors appear in the JS console

Offline tests

In a private iOS tab (memory-only storage), turn off the network.
Send a message and verify it appears with the offline/pending style.
Restore the network and verify the message sends.
Note: with memory-only storage the queue does not survive a reload. That is the expected consequence of the browser denying persistent storage.

QA Steps

Same as tests.

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

Nagranie.z.ekranu.2026-09-28.o.12.31.49.mov

MacOS: Chrome / Safari

github-actions · 2026-09-14T12:41:07Z

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

…le-fallback

chrispader · 2026-09-21T15:17:45Z

@sosek108 Onyx version 3.0.112 has been published. Please let me know when this PR is ready 🙌🏼

#101568 further bumps Onyx to version 3.0.113, so I'll hold on your PR 🙌🏼

sosek108 · 2026-09-22T07:23:32Z

@chrispader This PR is in Draft because target changes are not yet merged. So this will not be in 3.0.113. So maybe don't wait on me. cc: @fabioh8010

We create draft PRs for each change to keep an eye on CI checks whether Onyx changesdoes not break anything in E/App

chrispader · 2026-09-22T07:52:08Z

Ahh sorry nevermind, i though 3.1.112 was authored by you. Thanks for the clarification!

Resolve main conflict and pin react-native-onyx 3.0.115 for Expensify#101085

melvin-bot · 2026-09-28T10:26:42Z

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

…le-fallback # Conflicts: # package-lock.json # package.json

getusha · 2026-10-02T20:07:59Z

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
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 proper code patterns were followed (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 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)
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately
- 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
- 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 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 the PR adds or modifies the UI:
- I asked an AI agent to review the changes for accessibility issues and addressed its findings.
- I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
- I verified all new/changed elements have meaningful accessible names and roles.
- I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
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: mWeb Chrome

Screen.Recording.iPhone.17.Pro.02-10-2026.at.11.06.13.PM.mp4

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

sosek108 · 2026-10-05T07:40:36Z

@mountiny This PR got accepted by C+. Can you take a look?

mountiny

Thanks!

github-actions · 2026-10-05T14:10:10Z

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

OSBotify · 2026-10-05T14:11:35Z

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

github-actions · 2026-10-05T14:14:43Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ade1801-bee022e-c090afccfcce1dc5bed1cc4bd2afde362c86cd63/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ade1801-bee022e-9fe1861b853cb1cb0eafa1c54b8a3ccf2dcf3340/index.html

Web 🕸️
https://101085.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

OSBotify · 2026-10-05T23:35:18Z

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

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

kavimuru · 2026-10-05T23:43:51Z

@sosek108 how to check the logs for iPhone safari or chrome?
Check the console: exactly one degrade log, plus Storage operation skipped retry; the storage engine is unavailable... info logs for writes. No Can't find variable: indexedDB ReferenceError, and no Storage operation failed after N retries alerts.

If that to be done by remote debugging explain in detail what to check please?

sosek108 · 2026-10-06T07:36:22Z

@kavimuru To be honest I didn't think this through. Checking logs on non-dev build is hard. Let's do this way:

please verify other steps without checking the logs.
share with me test account's email and approximate timeframe of tests. I'll check logs on server

kavimuru · 2026-10-06T20:00:22Z

This PR was validated at around 8:40 am EST and email used is testing210790+ghu@gmail.com

OSBotify · 2026-10-06T21:56:05Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.5.3-4 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

sosek108 · 2026-10-07T07:57:29Z

@kavimuru Logging is as expected for this one. Thanks!

Pin Onyx to IndexedDB-unavailable fallback PR head

97dce07

melvin-bot Bot assigned sosek108 Sep 14, 2026

sosek108 mentioned this pull request Sep 14, 2026

fix(storage): degrade to memory-only when IndexedDB is unavailable Expensify/react-native-onyx#845

Merged

42 tasks done

Repin Onyx to latest PR head

d871dfb

sosek108 changed the title ~~[No QA] Pin Onyx to IndexedDB-unavailable fallback PR~~ [Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR Sep 16, 2026

sosek108 added 2 commits September 16, 2026 09:44

Merge remote-tracking branch 'exfy/main' into fix/indexeddb-unavailab…

fe48b61

…le-fallback

Repin Onyx to IndexedDB fallback PR head 47d155cb7

47337f8

fabioh8010 mentioned this pull request Sep 28, 2026

[Tracking] Onyx Improvements #80355

Open

Bump react-native-onyx to 3.0.115

815762a

sosek108 mentioned this pull request Sep 28, 2026

Resolve main conflict and pin react-native-onyx 3.0.115 for Expensify/App#101085 callstack-internal/Expensify-App#75

Merged

Merge pull request #75 from callstack-internal/fix/onyx-bump-3.0.115

0d80ac4

Resolve main conflict and pin react-native-onyx 3.0.115 for Expensify#101085

sosek108 changed the title ~~[Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR~~ [No QA][Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR Sep 28, 2026

sosek108 changed the title ~~[No QA][Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR~~ [Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR Sep 28, 2026

sosek108 changed the title ~~[Onyx bump] Pin Onyx to IndexedDB-unavailable fallback PR~~ [Onyx bump] Bump react-native-onyx to 3.0.115 Sep 28, 2026

sosek108 marked this pull request as ready for review September 28, 2026 10:26

sosek108 requested a review from a team as a code owner September 28, 2026 10:26

melvin-bot Bot requested review from getusha and removed request for a team September 28, 2026 10:26

sosek108 marked this pull request as draft September 28, 2026 10:28

sosek108 changed the title ~~[Onyx bump] Bump react-native-onyx to 3.0.115~~ [Hold][Onyx bump] Bump react-native-onyx to 3.0.115 Sep 28, 2026

sosek108 changed the title ~~[Hold][Onyx bump] Bump react-native-onyx to 3.0.115~~ [Onyx bump] Bump react-native-onyx to 3.0.115 Sep 30, 2026

sosek108 marked this pull request as ready for review September 30, 2026 07:51

sosek108 added 2 commits October 1, 2026 09:34

Merge branch 'main' into fix/indexeddb-unavailable-fallback

b855225

Restore GitHub Action bundles from main

6a265ec

sosek108 mentioned this pull request Oct 1, 2026

[Onyx bump] Bump react-native-onyx to 3.0.116 #101171

Merged

43 tasks done

This was referenced Oct 1, 2026

[Onyx bump] Bump react-native-onyx to 3.0.118 #102530

Draft

[Due for payment 2026-10-13] [Sentry: APP-B65] No fallback when indexedDB is unavailable, causing a rejection retry loop #100844

Open

Merge remote-tracking branch 'exfy/main' into fix/indexeddb-unavailab…

db95a76

…le-fallback # Conflicts: # package-lock.json # package.json

mountiny self-requested a review October 2, 2026 12:57

getusha approved these changes Oct 2, 2026

View reviewed changes

mountiny approved these changes Oct 5, 2026

View reviewed changes

mountiny merged commit ade1801 into Expensify:main Oct 5, 2026
41 of 43 checks passed

This was referenced Oct 5, 2026

Open workspace confirmation from the FAB on Account and Insights tabs #102625

Merged

Show list report fields when disabledOptions is shorter than values #103060

Merged

OSBotify mentioned this pull request Oct 5, 2026

Deploy Checklist: New Expensify 2026-10-05 #103094

Closed

93 tasks done

Conversation

sosek108 commented Sep 14, 2026 • 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 Sep 14, 2026

Uh oh!

chrispader commented Sep 21, 2026

Uh oh!

sosek108 commented Sep 22, 2026

Uh oh!

chrispader commented Sep 22, 2026

Uh oh!

melvin-bot Bot commented Sep 28, 2026

Uh oh!

getusha commented Oct 2, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

sosek108 commented Oct 5, 2026

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Oct 5, 2026

Uh oh!

OSBotify commented Oct 5, 2026

Uh oh!

github-actions Bot commented Oct 5, 2026

Uh oh!

OSBotify commented Oct 5, 2026

Uh oh!

kavimuru commented Oct 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sosek108 commented Oct 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kavimuru commented Oct 6, 2026

Uh oh!

OSBotify commented Oct 6, 2026

Uh oh!

sosek108 commented Oct 7, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

sosek108 commented Sep 14, 2026 •

edited

Loading

kavimuru commented Oct 5, 2026 •

edited

Loading

sosek108 commented Oct 6, 2026 •

edited

Loading