I tried back porting the changes specified here onto the `1.0.4` release but I'm getting the same behavior as specified earlier with `release/1.2.2` (unofficial) in that I'm requesting a finite number of documentIDs in the pull replication and it looks like I'm receiving the whole database. Additionally on the device the replication still hangs and never finishes. The device is an iPad 2 is running iOS 9.3.1.
One discrepancy using the iOS 9.3 simulator is that the replication does finish although it is receiving the whole database instead of the named replication. I'm not sure if I have any devices with iOS 9.3 anymore but I can try to test to see if part of the problem is between iOS versions. Let me know if you have any other suggestions. Thanks for your help as always Jens. On Friday, April 15, 2016 at 6:02:26 PM UTC-7, David Quon wrote: > > Thanks for the explanation Jens. So we tested with `release/1.2.2` > (unofficial) and we're noticing that the replication is pulling everything > (or it seems) and not just the `documentIDs` requested. Also the > replication does replicate a lot of documents (807 when we only requested > 693) before just hanging and replication never finished. Are these known > issues? > > We'll investigate the porting alternatives you suggested. Thanks for your > help as always. > > On Friday, April 15, 2016 at 11:52:47 AM UTC-7, Jens Alfke wrote: >> >> >> On Apr 14, 2016, at 6:25 PM, David Quon <[email protected]> wrote: >> >> CouchDB. I don't remember the exact version but let me know if that's >> important. >> >> >> Ah, that explains it. Older versions of CouchDB didn’t support POST to >> _changes, so older versions of Couchbase Lite sent it a GET instead. In 1.2 >> we switched to sending POST to CouchDB. Unfortunately there was a slight >> protocol incompatibility that made this not work (issue #1139); it’s >> recently been fixed on the master branch, and there’s also a (unofficial) >> `release/1.2.2` branch containing the fix. >> >> If you don’t want to upgrade all the way from 1.0.4 to >> 1.2-plus-unreleased-fixes ;) then you could edit the 1.0.4 sources so that >> CBLChangeTracker.usePOST is always set to YES in CBLPuller.m. At that point >> I think you’ll have the same problem as 1.2, so look at the patch that >> fixes #1139 and make a similar change (it’s minor; basically the _changes >> params should go into the URL as well as the POST body.) >> >> —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/528c9fe2-3226-4efa-92c8-0b78fac9fd4a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
