In rare cases documents with recycled ids are not pushed up

CBL 2.7.1 on Android
SG 2.7.3

This forum post from 3 years ago is similar to my situation. In my case the document ID is derived by the user entered content. This dramatically speeds up getting a document by its ID - if the contents are known - compared to running a N1QL query.

For a long time now I have been receiving user reports that recycled document IDs stop syncing. This seems to happen randomly. I was never able to face the same issue. Either by doing it manually over and over or by running automated ui tests. I was also never able to catch an exception in the Android app reported by a user or any at all with this specific issue:

for (ReplicatedDocument document : replication.getDocuments()) {
                    CouchbaseLiteException err = document.getError();
                    if (err != null) {
                    // log exception
                    }

And I could never find any log about a document which was rejected by SG fn even though I knew what document didn’t sync since I received user reports. I ran the grep command over SG logs similar to this:

grep -r "<user entered content>" *
grep -r "<document ID>" *

Recently I changed the architecture and document IDs are now created randomly. Before I go live with the update I’m happy to try another approach to somehow log the issue and to find the root cause.

2 posts - 2 participants

Read full topic