Couchbase Lite Sync Issue

Mobile
,
1

I’m experiencing a synchronization issue using Couchbase Lite 3.0.2 with Sync Gateway 2.8.
I have two environments: test and prod. The issue only occurs in production, and it happens intermittently, roughly 1 out of every 20 sync attempts +/-

**
**
Expected Behavior

A document should sync with the following structure:

{
“_id”: “3c21b161-zzzz-4e97-9181-800e76d8f90a”,
“_rev”: “4-5e3c1ca20a526c513179c7364f1zzzz”,
“base64Picture”: “large base64”,
“channels”: [
“channel1”,
“channel1”
],
“company”: “env-prod”,
“fresh”: false,
“parent”: “5ac9b2b4-zzzz-4789-b950-3d8eb4fd6d5c”,
“route”: “MetaData.images.socioeconomicIncomeData.businessFrontPhoto”,
“type”: “picture”
}

Actual Behavior

Occasionally, the document arrives like this:

{
“_id”: “b16e407e-9ed1-4db0-bf4e-c17e444be2f9”,
“_rev”: “1-952e07ec0f72f234609324665cbb2ffa”,
“fresh”: true
}

Sometimes the document doesn’t get created on the remote server at all, even though it appears correctly on the local device.

Observations

  • The issue does not occur in the test environment.

  • There’s no clear pattern to when it happens.

  • It affects about 1 in every 20 documents.

  • Sometimes the document doesn’t get created on the remote server at all, even though it appears correctly on the local device.

  • When the document does sync, it often arrives incomplete, missing fields like base64Picture, channels, type, etc.

  • It seems like the document is either partially synced or incorrectly created on the server.

Has anyone encountered a similar issue with Couchbase Lite and Sync Gateway?

2

Document sync operations are basically atomic so partial sync is pretty much out of the question aside from a catastrophic defect. There are a lot of unknowns here about how your environment is set up but aside from that please note that both of those versions are quite old at this point.