How do I resolve a document conflict for a document with two version 1?

Mobile Sync Gateway
1

Hi, I have a document that is public to all our users so it has been synced to everyone, but it has a conflict in it from when we first created our database years ago. Our current version of sync gateway is 1.3.1. The document has two version 1’s and two branches that both start at a different version 1 of the document. I tried to resolve the conflict in one of the branches by deleting the leaf node of it, but instead it created another leaf node for the deleted document (it just has body _deleted:true). How do I resolve this conflict so only one branch survives? I tried deleting the revision 1 of the branch I want pruned away, but it said doc revision conflict, and if I try to delete the new leaf node it created it just says document already deleted. I am trying to delete the branch that starts with 1-be1efc11d71669806e6ac50c43a394d5 and ends with 3-cdc822db581721ed8f1112868b05cf70. Here is the current _sync metadata for the document:
"_sync": {
“rev”: “11-ba9744c95bbdf7e9bde5014e597df96a”,
“new_rev”: “3-cdc822db581721ed8f1112868b05cf70”,
“flags”: 20,
“sequence”: 1820136,
“recent_sequences”: [
1739784,
1820136
],
“history”: {
“revs”: [
“4-743af3a712525c4a047403c54863aff2”,
“2-c0062a2b14a3244d2686912ce817af37”,
“1-1a3fc9d56f1d6b03cd149b7ade491bc9”,
“1-be1efc11d71669806e6ac50c43a394d5”,
“9-bf53e3bce16433c37deb6a7344d7f8a4”,
“10-1cde6a3328d1d674e30c694118b11681”,
“5-2989d29d2f599d8d0332b7493111b57b”,
“2-cb003de83e93930fd406012e741f54de”,
“6-69668266429b3e4539c14f2602b28826”,
“7-66f423f46bb2d70c58f123d5a1befbb2”,
“11-ba9744c95bbdf7e9bde5014e597df96a”,
“3-5143af6dffc89b94581aa873d055c35d”,
“8-3ca37f17b8df8a5af4765e5794970755”,
“3-cdc822db581721ed8f1112868b05cf70”
],
“parents”: [
11,
2,
-1,
-1,
12,
4,
0,
3,
6,
8,
5,
1,
9,
7
],
“deleted”: [
13
],
“bodymap”: {
“13”: “{”_deleted":true}"
},
…
}
}

2

Actually even though there is a branch with a leaf node that is just a deleted document the conflict seems to be resolved.

3

Hi, Deletions in Couchbase Mobile are treated as updates (they have a special _deleted flag). That is why, when you delete/tombstone a revision, it adds a new leaf node corresponding to the deleted revision. You can learn more about revision trees and tomb stoning in this blog post. Once you have tombstoned all conflicting leaf nodes except the winning revision , then the conflict is resolved.