I write a new Document to the Couchbase Lite database on iOS. I run a continuous push replicator to push this new Document to the server. Then I listen to the DocumentReplication event to Purge the Document from the client so it will only exist on the server. The Document ID is triggered in the event twice. The event fires, it contains the document ID, says it was pushed. Then the event fires again, contains the same document ID, says it was pushed. The 2nd time the document was already purged so it can no longer be purged (again). I can make a workaround to check if the document still exists, but
I am wondering if the event firing twice with the same document ID is a bug or a feature?