Sync is stuck - How to handle aborts/errors?

[sarink]

If dexie throws because a transaction failed or was aborted, I see a flood of this in the console

Failed to sync client changes TypeError: Cannot read properties of undefined (reading 'length')

error in syncIfPossible() TypeError: Cannot read properties of undefined (reading 'length')

DexieError2
{
    "name": "AbortError",
    "message": "The transaction was aborted, so the request cannot be fulfilled.\n AbortError: The transaction was aborted, so the request cannot be fulfilled.",
    "inner": {}
}

The problem is now the user is stuck permanently in this state, and no further updates or syncs can succeed.

What is the solution to recover?

[dfahlander]

Which version of dexie-cloud-addon are you using?

Does the log reveal any file and line number where this error happens? If not, could you open devtools, go to sources tab and check break on uncaught exception pinpoint the code location.

[sarink]

I'm using the latest version. I have identified where the error happens, but I still need a solution to detect this programmatically to fix affected clients.

[dfahlander]

In order to help you, I need to know the line number and file. This will help me find the issue and the reason.

If I get this information, I could publish a new version of dexie-cloud-addon with a fix but also understand the reason and suggest a workaround if you prefer.

[sarink]

@dfahlander does this stack trace help? I'm not exactly sure what you need

  | overrideMethod | @ | installHook.js:1
  | (anonymous) | @ | chunk-BNXH64T3.js?v=7ef9e871:1364
  | (anonymous) | @ | chunk-BNXH64T3.js?v=7ef9e871:1087
  | (anonymous) | @ | chunk-BNXH64T3.js?v=7ef9e871:857
  | callListener | @ | chunk-BNXH64T3.js?v=7ef9e871:856
  | endMicroTickScope | @ | chunk-BNXH64T3.js?v=7ef9e871:891
  | (anonymous) | @ | chunk-BNXH64T3.js?v=7ef9e871:950
  | Dexie: read $drinks_mutations |   |  
  | Table2._trans | @ | chunk-BNXH64T3.js?v=7ef9e871:1350
  | Collection2._read | @ | chunk-BNXH64T3.js?v=7ef9e871:1928
  | Collection2.toArray | @ | chunk-BNXH64T3.js?v=7ef9e871:2002
  | Table2.toArray | @ | chunk-BNXH64T3.js?v=7ef9e871:1454
  | (anonymous) | @ | dexie-cloud-addon.js?v=7ef9e871:12469
  | (anonymous) | @ | dexie-cloud-addon.js?v=7ef9e871:11110
  | executePromiseTask | @ | chunk-BNXH64T3.js?v=7ef9e871:787
  | DexiePromise | @ | chunk-BNXH64T3.js?v=7ef9e871:588
  | __awaiter2 | @ | dexie-cloud-addon.js?v=7ef9e871:11092
  | (anonymous) | @ | dexie-cloud-addon.js?v=7ef9e871:12463
  | (anonymous) | @ | dexie-cloud-addon.js?v=7ef9e871:12463
  | (anonymous) | @ | dexie-cloud-addon.js?v=7ef9e871:11110
  | executePromiseTask | @ | chunk-BNXH64T3.js?v=7ef9e871:787

[dfahlander]

This stack is heavily optimized but it actually gives some hints. Issue seem to be happening after reading table $drinks_mutations. Could be if that table contains invalid content. Would you mind extracting the data from that table? If so, run the following in devtools console:

Dexie = self[Symbol.for("Dexie")]; // imports Dexie by local symbol
db = Dexie.connections[0]; // Get the instance.
mutations = await db.$drinks_mutations.toArray(); // List all $drinks_mutations
JSON.stringify(mutations, null, 2); // Print the JSON for it

It might reveal whether the data in that table has unexpected null or undefined properties that we need to take care of.

[dfahlander]

I'm trying to get to the bottom with the problem by code review only but cannot see any obvious place. Hints from your data would help very much. Also one thing of interest would be your parameters to db.cloud.configure() such as whether unsyncedTables or unsyncedProperties is specified.

[dfahlander]

Created an issue #2228 for this working on reproducing it.

[dfahlander]

Issue fixed in dexie-cloud-addon@4.2.5