Thanks for the reply. That was indeed the problem: I was using a background thread.
It kind of sucks that I have to keep calling the runloop's run() function from a timer just to get access to the notifications because I'm using this thread for other long-term operations. (Once I did that, the notifications started coming back again). Does anybody have a better solution to avoid polling the runloop for CBL notifications? Is anyone else using CBL in a background thread? - Michael On Saturday, August 23, 2014 2:03:49 AM UTC+8, Jens Alfke wrote: > > > > On Aug 22, 2014, at 9:39 AM, Michael Hines <[email protected] > <javascript:>> wrote: > > > > Any ideas why I'm not getting any future change notifications? > > Are you starting the replication on the main thread? If not: > If you run it on a background thread, does it have an active > runloop? > Or if you're using a dispatch queue, have you set the CBLManager's > dispatchQueue property? > > Does the object that contains those two methods stay around long enough? > If it's dealloced, it won't get any further notifications. > > —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/f55fba5f-8a72-42a9-8dee-768697e0d057%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
