• developer

    @schiri said in davx5 not syncing tasks with mailbox.org:


    2. Sync with DAVx⁵.

    5. Sync with DAVx⁵.

    Manual sync, I guess?

    Hence, my question is: what changed from 2.6.2 to 2.6.3(.1) that causes sync not working until some task was edited on the phone?

    Before c267c92a (see changes in last lines of SyncManager.kt; 27 Dec 2019; released with 2.6.3), forced (= manual) sync didn’t take the CTag/sync-token into account and (in PROPFIND/REPORT mode) always requested a full listing. Note that this is not consistent with automatic sync, because automatic sync always checks (and always has checked) the CTag/sync-token of a collection before synchronizing. When the CTag/sync-token didn’t change since the last synchronization, another synchronization is not required – that’s the whole reason for the existence of CTag [https://github.com/apple/ccs-calendarserver/blob/master/doc/Extensions/caldav-ctag.txt#L173] / sync-token [https://tools.ietf.org/html/rfc6578#section-3.5].

    In your case, a manual sync with ≤ 2.6.2 will synchronize the new tasks, but automatic synchronization will not. Can you verify that? Also, other clients won’t sync these new tasks, too (at least if they check CTag/sync-token before).

    So to summarize: since 2.6.3, manual sync behaves equally as automatic sync, and behaves like it is expected to do.

    I am going to check the 2.6.2-ose version because it would be great to be solved in that version…

    The problem won’t be solved, but it can be worked around if you do manual syncs whenever you want new tasks to appear.


  • @rfc2822 said in davx5 not syncing tasks with mailbox.org:


    2. Sync with DAVx⁵.

    5. Sync with DAVx⁵.

    Manual sync, I guess?

    Yes, you are correct, these were manual syncs to speed up the testing process.

    @rfc2822 said in davx5 not syncing tasks with mailbox.org:

    In your case, a manual sync with ≤ 2.6.2 will synchronize the new tasks, but automatic synchronization will not. Can you verify that?

    Verified. Only manual syncs received the new tasks, not automatic syncs.

    I’ll stick with 2.6.2 to have an opportunity to get in sync manually until the issue is solved with OX. @chrpinedo, if possible please tell them that the issue does not seem to occur with server version: 7.10.1-Rev25, but later. Btw., can you check which server version is current for mailbox.org? Should be visible in the webmail, menu > about.


  • @schiri They closed my ticket because they considered the bug was going to requite quite time to be resolved. And they didn’t tell me the version they use of OX. I am a sysadmin and I would not consider reasonable to downgrade the server version for a “minor bug”.

    If you can, it would be good to open a bug ticket with “1&1 IONOS”, because if OX receives the same bug from different customers, they probably will try to solve this issue faster.


  • It works with 1&1 IONOS, so no need to bother them 😉
    I’ll let OX know about the issue anyway as our self-hosted instance is a commercial one as well.

    My comment about the version was not to make them downgrade, but give them an impression about when the functionality broke. Can you please check the version in the mailbox.org web interface under menu > about? If it is > 7.10.1, it would support my assumption.


  • @schiri I’m also affected by this OX bug.

    Right now syncing between DAVx5 on Android and even on my Desktop PC with Evolution is not working.

    I’ve checked the OX Version in the mailbox.org web interface: Server-Version: 7.10.2-Rev20


  • @shellshocker if you can, open a support ticket with mailbox.org as I did just to push so that they solve the issue ASAP … Regards

  • developer

    Seems that this has been fixed at mailbox.org now. Can you confirm that?


  • I tried today and it didn’t work for me. I didn’t receive any notification from mailbox.org either.

    My test:

    • I updated Dav5x to version 2.6.5
    • I created a new task in my PC
    • the task didn’t sync to my android device, even I forced the sync from dav5x
    • If a create a new task in my android device, then the task in synced

    Regards,

  • developer

    I have tried with our mailbox.org test account:

    1. sync-token is 1584973865082.
    2. Then I created a new task in the Web UI.
    3. sync-token is now 1584973939914,
    4. so the task is synced by DAVx5.

    Same for modified tasks.


  • @rfc2822 In my test, at the second point, in order to create the test task I didn’t use the mailbox.org webpage, thunderbird task manager (lighting) instead.

  • developer

    @chrpinedo I see. So this might be another problem like the original one.

  • developer

    I have tested with Thunderbird, and this works here, too:

    1. Sync with DAVx5
    2. Create/edit task in Thunderbird
    3. Sync again with DAVx5
    4. New/modified task appears in OpenTasks

    mailbox.org server version 7.10.2-Rev22

  • admin

    @chrpinedo said in davx5 not syncing tasks with mailbox.org:

    @rfc2822 In my test, at the second point, in order to create the test task I didn’t use the mailbox.org webpage, thunderbird task manager (lighting) instead.

    Are you sure that you put the task in the right task list in Thunderbird? There is a drop-down to choose the “Calendar” where the task should be stored. We used Lightning 68.4.1


  • Digging out this topic again as I’m keen to update to 3.0. I am on OX server version 7.10.2-Rev23, so it seems to be fixed according to your latest comments. Though, before updating Davx5, I’d like to check if sync works properly with my OX version.

    @chrpinedo @rfc2822 @shellshocker: Does it work for you? Which OX version is mailbox.org running currently?


  • I interpret radio silence as: Yup, works as expected with mailbox.org. Please correct me if I’m wrong. 😀


  • OK, took the dangerous route and installed DAVx5 3.0 😇
    Can confirm that tasks sync correctly with OX server versions 7.10.2-Rev22 and 7.10.2-Rev25, which are my current installation - except for recurring tasks.

    According to the OX release notes, the following bug fix filters out recurring tasks on the CalDAV interface from 7.10.2-rev23 on:
    "MWB-103 Recurring tasks can not be marked as done via EM Client

    The caldav servlet doesn’t support operations on recurring tasks, but it also doesn’t filter recurring tasks out.This has been resolved by just filtering thoes recurring tasks."

    That’s also what I can confirm: Recurring tasks on the Rev22 installation show up while those on the Rev25 installation are only visible in the OX web interface.

    Hope this might help the one or the other having trouble.

  • admin

    @schiri thank you for digging into this and reporting the outcome here. very appreciated! Glad that there is no issue on our side 😄 Recurring tasks and sub-tasks are supported in acalendar+ tasks and can be synced via DAVx5.

Similar topics