You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just noticed that CBLReplicator's callbacks all run on the main dispatch queue, since its _dispatchQueue ivar is initialized to dispatch_get_main_queue() and never changed.
This could block UI work the main queue is doing, or if the main queue is overly busy it could delay the replicator.
I think it'd be better to set _dispatchQueue to be the queue of the local CBLDatabase associated with the replicator.
The text was updated successfully, but these errors were encountered:
…t API
* Made CBLReplicator.status property atomic (#2187)
* Changed CBLReplicator to use the dispatch queue from the CBLDatabase instead of using Main queue (#2127)
Just noticed that CBLReplicator's callbacks all run on the main dispatch queue, since its
_dispatchQueue
ivar is initialized todispatch_get_main_queue()
and never changed.This could block UI work the main queue is doing, or if the main queue is overly busy it could delay the replicator.
I think it'd be better to set
_dispatchQueue
to be the queue of the localCBLDatabase
associated with the replicator.The text was updated successfully, but these errors were encountered: