Details
Minor Description
On encountering an unrecoverable error, Core changes its state to STOPPED. Before it does that, however, it often reports a state change to listeners that report that it is in the BUSY state but also contain the unrecoverable error.
That's inconsistent.
When the state changes to STOPPED, LiteCore continues to report the error that casued the state change, so the report in the BUSY state is probably not terribly significant.
An application that assumes that the report of a failure, to a listener, implies that the reporting replicator has stopped, though, will be surprised.