@Giallon Hmmm… interesting.
Can you give me a little bit more log? Those 4 lines are not enough to identify the location of the bug. Can you set the debug level to at least VERBOSE and provide logs for the whole connection process?
In particular, I need the log line (v2.8.5) that looks like this:
I/CouchbaseLite/NETWORK: WebSocket CLOSED …
… and I do believe that this is probably a bug.
FWIW, here is what I believe is happening:
When the remote is disconnected, OkHttp, the package we use for websocket communication, reports the error code that it gets from the OS. The OS uses POSIX codes which, perhaps surprisingly, are platform dependent! In the process of correcting how some failures are reported, I inadvertently made Android (where we can identify the POSIX code) report connection failure as an unknown failure type. Core, which manages the replicator, considers an unknown failure unrecoverable.