[Bug] Document deletion is not synced to offline client after reconnection (Data inconsistency)

[asher-syncsoft]

Description:
I am encountering a synchronization issue with deleted documents when one device is offline.

Scenario 1 (Online - Working): When Device A and Device B are both online with the Replicator active, deleting a document on Device A immediately deletes it on Device B. This works as expected.

Scenario 2 (Offline - Failing):

Both Device A and Device B have the same document.

Device B goes offline (App closed/killed).

I delete the document on Device A.

The deletion is synced to the server (checked on Couchbase Capella, the document is correctly deleted/marked as tombstone).

Device B comes online (App opened, Replicator starts).

Result: Device B still retrieves the deleted document via query. It seems the deletion event (tombstone) is not being pulled or processed correctly by Device B upon reconnection.

Steps to Reproduce:

1. Initialize cbl-reactnative on Device A and Device B. Connect both to the same Capella bucket.

2. Wait for all documents to sync to Device A and B.

3. Kill the app on Device B (simulate offline/inactive state).

4. Delete doc_1 on Device A.

5. Verify on Couchbase Capella dashboard that doc_1 is deleted.

6. Open the app on Device B. Wait for the Replicator to finish connecting.

7. Run a query on Device B to fetch doc_1.

Observed: doc_1 is still returned in the query results on Device B.

Expected: doc_1 should be removed from Device B's local database after the Replicator pulls the changes.

Environment Info:
Library Version: cbl-reactnative 0.6.3

React Native Version: 0.74.5

Platform: (iOS 18.3 / Simulator)

Server: Couchbase Capella

Replicator Config:

Type: PushAndPull

Continuous: true

Method use to delete document
await airportCollection.deleteDocument(document);

Source code:
DemoCBApp.zip

Video demo
https://drive.google.com/file/d/19ZHIl7wwbIugwfBSdsz5lghmjFLRCy9W/view?usp=sharing

[jayant-dhingra-cb]

Hey,

Can you please Share CBL mobile Logs and capella Logs ?
Also can you please share your xcode version

[jayant-dhingra-cb]

We tried with your code, everything is working on our side.

We used Xcode version 26
React native version - 0.81.5

We noticed your version was 0.75 but as per our docs we recommend you using 0.76.3

If you could share the logs, it would be better for us to check

[asher-syncsoft]

@jayant-dhingra-cb Here is a video demo using React native version 0.76.3 as you recommend. I still faced with this issue: https://drive.google.com/file/d/15dWdYkK-5slrHhkp4ppOM-UAkHeZpGXl/view?usp=sharing

And this is log when I deleted doc:

[jayant-dhingra-cb]

Thanks for the react native logs.

Can you please provide the following

1. Capella logs
2. Xcode version

Also, are you facing this issue only in iOS, or you are facing in Android as well ?

[asher-syncsoft]

@jayant-dhingra-cb
I don't have the Capella logs yet. I am using Xcode version 16.2, and the app is currently iOS-only

[jayant-dhingra-cb]

@asher-syncsoft I tried replicating your issue, now I was able to replicate but check the video

As per your point 6 you just wait for replicator connection but after replicator is connected you need to wait to sync the data from Capella which might take couple of seconds.

After the syncing is done, you probably won't face this issue (check video)

Also we used new pre-released version for cbl-reactnative, please try to use that.

Check the video link
https://drive.google.com/file/d/1xSCz4c5ETpNmaPk1iLTnc8p3FBmuo5Z0/view?usp=sharing

I have updated the code and added UI for sync completion
https://drive.google.com/file/d/1afsnTLK9icHkmXyfXZXaaviOTdnb_m6l/view?usp=sharing

[jayant-dhingra-cb]

Hey, I believe with the above code, your issue is resolved. Can you please give me a confirmation to close the ticket?

[asher-syncsoft]

hi @jayant-dhingra-cb , At the moment, it looks like the issue has been resolved on the demo project, but our main project is still facing the issue.
I’ve also tried the pre-release version of cbl-react-native you shared on my main project, but it doesn’t work there.
I’m currently trying alternative approaches to fix it on the main project and will update you once I have progress.