[Bug] CalDAV / CardDAV off-peak interval resets itself when reviewed [released]

asked 2019-12-29 19:32:29 +0200

stateoftheart gravatar image

somewhat related to: https://together.jolla.com/question/126146/bug-manual-off-peak-email-synchronisation-settings-are-not-respected/

Steps to reproduce:

1) Change the "Sync content" setting of a CalDAV / CardDAV Account to "Custom".

2) Change the "Off-peak interval" to "Manually". (Anything other than "Twice a day" will reveal the bug, even the default of "Every 15 Minute")

3) Pull left (back to Accounts overview) to save the settings.

-> It gets correctly saved like this in '/home/nemo/.cache/msyncd/sync/carddav.Contacts-4.xml' and '/home/nemo/.cache/msyncd/sync/caldav-sync-4.xml':

<schedule days="4,5,6,7,1,2,3" enabled="true" time="" syncconfiguredtime="" interval="0">
    <rush externalsync="false" days="4,5,1,2,3" enabled="true" begin="09:00:00" end="17:00:00" interval="15"/>
</schedule>

4) Review the settings (access the CalDAV/CardDAV Account again)

-> The off-peak interval now holds "Twice a day". (bug) This will also get saved when pulling left (back to the Accounts overview) without changing anything:

<schedule days="4,5,6,7,1,2,3" enabled="true" time="" syncconfiguredtime="" interval="720">
    <rush externalsync="false" days="4,5,1,2,3" enabled="true" begin="09:00:00" end="17:00:00" interval="15"/>
</schedule>

The other CalDAV / CardDAV settings do not behave like this.

edit retag flag offensive reopen delete

The question has been closed for the following reason "released in a software update" by stateoftheart
close date 2020-04-04 14:23:00.955614

Comments

1

Same here. First I thought I made a mistake. But after creating the same account three times with "manual" always with the result "two times a day" I realised: this is probably a bug. Thank you for reporting this issue.

dirksche ( 2019-12-29 20:15:26 +0200 )edit
2

This bug will be fixed in a coming release > 3.2.1. It has a merge request upstream.

Damien Caliste ( 2019-12-30 00:31:44 +0200 )edit

Thank you Damien for this information. I will close this thread when the fix is released.

stateoftheart ( 2019-12-30 09:53:09 +0200 )edit

"This bug will be fixed in a coming release > 3.2.1. It has a merge request upstream."

We will see :-)

dirksche ( 2019-12-30 12:25:05 +0200 )edit