Yes, I've stepped through it. So what's happening is, the current revision is the one with the big number, e.g. 4206. The conflicted revision is the 1-409 revision. A new revision is created and then since it's not the current revision, the 1-409 revision is getting its "isDeletion" flag set to YES. And then I call [newRev saveAllowingConflict:] on the new revision. That succeeds without error. But then the next time the pull replication goes idle, offline, or stopped, I process all the conflicting documents again and we're back at square one.
Thanks, Brendan On Thursday, April 14, 2016 at 2:43:02 PM UTC-6, Jens Alfke wrote: > > > On Apr 14, 2016, at 1:19 PM, Brendan Duddridge <[email protected] > <javascript:>> wrote: > > CBLSavedRevision[rec-..fb1b/1-4098dccaa969cdbab64825e687aaec68], > > CBLSavedRevision[rec-..fb1b/4206-5128082a4eb2783ba5e60116f84f7e07] > > But each time through the above loop, a new revision is being added, so > 4206 becomes 4207, ... n. and so on. > > > So the 1-409… revision isn’t being deleted? The code in your previous > message should end up deleting it. Have you tried stepping through it to > see what’s going on? > > —Jens > -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/2fde1368-1ddd-41a3-885d-7d9b86cd8663%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
