[Due for payment 2025-12-30] Improve handling of `Failed to execute 'put' on 'IDBObjectStore'` error

[VickyStash]

We have a lot of reports in Sentry with Failed to execute 'put' on 'IDBObjectStore' error reported: https://expensify.sentry.io/issues/6998316400/events/ad8318ed6ad3464ca7e343d1aa50cbab/events/?project=4510228107427840&query=user.email%3Ateam%40truehopecambodia.org&referrer=previous-event

Why this error is triggered:
This error occurs when non-serializable data is passed to Onyx. You can reproduce it on your end by pasting Onyx.set('bad', {test: new FormData()}); to the console on dev/staging.

TODOs:

1. Define why this error was triggered for the users. What kind of the data was trying to be set to Onyx.
2. Improve the handling of this error on the Onyx side not to throw an error. Just logging of the alert should be enough.

Issue Owner

Current Issue Owner: @mallenexpensify

[melvin-bot]

Triggered auto assignment to @mallenexpensify (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.

[pasyukevich]

I would like to work on it

[pasyukevich]

Updates:

• The error Failed to execute 'put' on 'IDBObjectStore': function () { [native code] } could not be cloned appears on multiple pages, including profile settings and report pages, where files are uploaded. (Looks like it can be connected with the file uploading)
• Continue looking for the root cause

[pasyukevich]

Updates:

• The theory from yesterday doesn’t seem valid.
• Sentry Logs show that the problem mostly occurs during periods of user inactivity.
• Continue looking for the root cause

[pasyukevich]

Updates:

• I was able to reproduce the issue on staging only by opening the app after 24 hours of inactivity — this triggers a full freeze and makes the app unusable.
• Reviewed additional logs: some users encounter this issue during normal app usage as well.
• The issue does not appear to depend on what the user is doing at the moment.
• All other attempted reproduction scenarios did not lead to the issue.

[pasyukevich]

I was able to reproduce the issue on prod too - that's how it looks from the user perspective (after 3-4 minutes freeze)

Refreshing the page does not help