New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replication.CompletedChangesCount is always 0 #438
Comments
Could you post a bit more of your logs? Are you using Sync Gateway? If so, what version? |
This is the only relevant information from the logs. We're using sync gateway version 1.0.3. I'm not sure if this combination is supported or not, but it seems to work fine except for this error. I'm showing a progress bar to the user that's populated like this:
This used to work great, but now CompletedChangesCount is always 0, even when ChangesCount is non-zero and documents are being replicated down. |
In general we recommend users to keep up with the latest versions, if possible. I'll see if I can reproduce this with 1.1. |
@ryanthompson0123 I've noticed that sometimes things can be called in a confusing order. I tried running my unit test which runs on the completed changes count, and the count did change, but not until after the status was changed to idle (or stopped). Could this possibly be causing the trouble you are having? |
@ryanthompson0123 I've made a substantial refactor to the replication code base, and pushed it to a branch called |
@borrrden Thanks! I will take a look at it on Monday 7/13. I did take your advice though and wait until the after the status change to get the count, and that started giving me results, but I still see that error message showing up in the logs. |
First off, when I built the iOS solution I had to manually add the Stateless NuGet package to get it to compile. I'm not sure if that's by design, or just needs to be added to the solution in git, but I wanted to let you know. As far as using it, the actual changes counts seem much more reliable now, and they come in when I would expect them to. However, there's still an error being spit out to the console, but it's slightly different than before. Here's my logs (lines starting with "PULL" and "REPLICATOR" are my own logging statements that trigger when Replication.Changed is fired, everything else is coming from Couchbase Lite):
At this point, this doesn't seem to be causing me any issues, the log messages are the only symptom. |
Doh, no of course that was not intentional. That's a symptom of my tunnel vision. I'm worried about that log message though. Are the documents that throw those messages getting synced properly? That message looks like you have docs stored in the remote DB without an |
I'm going to close this ticket since the log messages are probably not related to this issue in particular. |
Using version 1.1.0.1 in my Xamarin apps, the completed changes count always shows 0 during replication. The following error is printed to the console lots of times during replication and I think it's related:
The text was updated successfully, but these errors were encountered: