[Due for payment 2025-10-17] Web App stuck on the splash screen

[mountiny]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @heyjennahay
Slack conversation (hyperlinked to channel name): https://expensify.slack.com/archives/C05LX9D6E07/p1756832229019399

Action Performed:

Break down in numbered steps

1. try to load the web app
2. Be stuck on this page

Console shows out of storage in onyx

Expected Result:

Describe what you think should've happened

We should be able to handle this gracefully and recover from it

Actual Result:

Describe what actually happened

User is stuck until thye clear the storage of the app which is not really feasible for normal user

Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

Platforms:

Select the officially supported platforms where the issue was reproduced:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Platforms Tested:

On which of our officially supported platforms was this issue tested:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @NicMendonca

[melvin-bot]

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @neil-marcellini (AutoAssignerNewDotQuality)

[mountiny]

@zirgulis is investigating as top priority, check out the thread for more details

[zirgulis]

@mountiny I have a draft PR open but I need to do more testing. Will have this ready for review tomorrow morning.

[zirgulis]

@mountiny @fabioh8010 Today I was testing my PR while trying to reproduce this "Out of Storage" issue and see if it catches the uncaught error. Since I was not able to reproduce this exact error on neither platform, I instead tested this by deleting the OnyxDB in Devtools > Application and got a similar error: Uncaught (in promise) InvalidStateError: Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.

The issue with these errors is that they are coming from the idb-keyval library which by design creates Promise chains with synchronous IndexedDB operations inside .then() callbacks, which can throw before our error handling is set up. This is a fundamental limitation of the library's architecture that we cannot fix from the outside without modifying the library itself or using global error handlers.

Root cause analysis:
The uncaught Promise rejections occur in this sequence:

1. idb-keyval calls db.transaction('keyvaluepairs', 'readwrite') inside a Promise .then() callback
2. IndexedDB throws a synchronous error when the database is corrupted/closing
3. This creates an uncaught Promise rejection at the browser level before our error handlers can attach
4. Our tryOrDegradePerformance wrapper eventually catches the error, but the app is already broken

Options to avoid these errors:

1. Fork/patch idb-keyval: modify the library's functions to use proper async/await error handling instead of Promise chains with synchronous IndexedDB operations
2. Improve eviction rules/logic : make Onyx more aggressive about removing cached data before storage becomes full, reducing the frequency of storage quota errors that trigger the uncaught rejections

[mountiny]

I am not sure if forking that library is the best approach for us. Do you know which data is growing so much in onyx to lead to this error?

Could you try to get a clear Problem and share that in slack with some alternative solutions too? Would moving to sqlite on web too help?

[melvin-bot]

@zirgulis Whoops! This issue is 2 days overdue. Let's get this updated quick!