Hi,

We are currently testing corner cases in our QA cycle and ran into an issue 
with the kCBLReplicationStatus. We are using a one-off replication scenario 
against a non-existing target to verify whether our app throws the correct 
error. However when using a remote target the timeout never happens.

Scenario:
Non-existing target: *http://127.0.0.1:8888* => replication stops after a 
~10sec timeout
Non-existing target: *http://dev.server.com:8888* ==> replication never 
stops but shows kCBLReplicationStatusOffline status

The same issue occurs with any other remote server such as 
http://www.google.com (don't tell them we tried that).

Is there anything we are missing with regards to how the replication is 
suppose to timeout when a remote server is not available?

We are using Couchbase Mobile 1.0.3.1

Thanks

-- 
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/5cbc30a5-1417-4c15-b354-f465a71ea04e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to