On Feb 13, 2014, at 3:41 AM, Endika Montejo <[email protected]<mailto:[email protected]>> wrote:
- When I create the replication I don't start the pusher and the puller, but the replication works. (From what I have read the replication must be started) New replications must be started. You made the replications persistent, so on the next launch of the app the replications already exist and start automatically without your intervention. I recommend not making the replications persistent. Post-beta-2 we've actually removed the concept of persistent replications. It was a feature that came from CouchDB, but it's not really useful in an embedded database and it makes the code and the API more complex. - Even when I stop asynchronously the replication, it keeps working. You may have multiple replications running. You used "exclusively:NO" so when you create the replications other pre-existing replications to different URLs won't be removed. If you've ever changed the remote URL, you may still have persistent replications left over that are still replicating with the old URL. To make sure old persistent replications aren't left behind, I recommend deleting your app from the device/simulator, then running the app again. (After taking out the line that makes the replications persistent.) - In the observer I log the completedChangesCount and changesCount of both pusher and puller and I always get a 0 in both properties. You're observing the key path "completed" when the property name is "completedChangesCount", so you're not getting called when the property changes. --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/74B04707-49E6-4998-AAC3-582F1B2B5683%40couchbase.com. For more options, visit https://groups.google.com/groups/opt_out.
