I'm running into an issue with handling errors with replication with the latest sync gateway and 1.1 or greater CBL.
During first login and sync, I'm using replicator change notifications to monitor the Replicator's lastError property, among others, to determine if an initial sync is complete. However, when an error occurs at sometime during sync, it's unclear when sync resumes error free, as opposed to continually retrying with the previous error. When the app goes offline, then online, this property seems to be reset. And with 401s, we restart replication. But with transient errors, like a few new 502s we're seeing from the new Sync Gateway, replication keeps going and retains the error. This causes our sync logic to assume the initial sync failed. While seems to reflect the properties name of "lastError", it makes it difficult to determine if sync went idle without an error. If I kill the app, which restarts replicator, this clears the property. Is there any other way to reset this value once the error has been read and handled other than a restart? Thanks, - Scott -- 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/1e0ae499-a7c4-4cd0-ad89-7605a0fe2ccb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
