I regularly get a Invalid .decsync-info notification which coincides with one of the calendars reporting a discrepancy like this:
Android entries 303DecSync entries 304
I have been using DecSyncCC for over a year, and I get this regularly. When I do, like now, there isn't much I can do to fix it, and the notification keeps appearing. I suppose this can continue forever, until the discrepancy in the number of entries is removed. I am not sure how I made it go away previously. I am guessing this may have something to do with #66 which I reported earlier, and possibly syncthing conflicts.
If the root cause can't be diagnosed/fixed, can DecSyncCC fall back to somehow forcing the two numbers of entries to be the same, even if that means an event being duplicated?
I regularly get a
Invalid .decsync-infonotification which coincides with one of the calendars reporting a discrepancy like this:Android entries 303DecSync entries 304I have been using DecSyncCC for over a year, and I get this regularly. When I do, like now, there isn't much I can do to fix it, and the notification keeps appearing. I suppose this can continue forever, until the discrepancy in the number of entries is removed. I am not sure how I made it go away previously. I am guessing this may have something to do with #66 which I reported earlier, and possibly syncthing conflicts.
If the root cause can't be diagnosed/fixed, can DecSyncCC fall back to somehow forcing the two numbers of entries to be the same, even if that means an event being duplicated?
Android 7, DecSyncCC 2.2.3