Reminder times synchronization with IOS

IOS 6 and 7 does not synchronize alert times correctly. If

Tue, 26 Nov 2013 23:29:27 +0000

IOS 6 and 7 does not synchronize alert times correctly. If I set an alert time on IOS, it changes to some random huge value like 8 days, 15 hours, 2 minutes before the event, and mixes first and second alert. From web interface to IOS seems to work, though.

Using which synchronization protocol?

Wed, 27 Nov 2013 00:00:56 +0000

Using which synchronization protocol?

> Using which synchronization protocol? Caldav, sorry.

Wed, 27 Nov 2013 00:05:03 +0000

> Using which synchronization protocol? Caldav, sorry.

Cannot reproduce on iOS 5, 6, or 7.

Wed, 27 Nov 2013 00:52:02 +0000

Cannot reproduce on iOS 5, 6, or 7.

...and what do you mean that it mixes first and second alert

Wed, 27 Nov 2013 00:55:58 +0000

...and what do you mean that it mixes first and second alerts?

> ...and what do you mean that it mixes first and second ale

Wed, 27 Nov 2013 01:19:48 +0000

> ...and what do you mean that it mixes first and second alerts? Not directly mixing, but adding when not requested, for example: All on IOS: Create event with alert at time of event. Then change alert to 15 minutes before. This creates two alerts, one with "at time of event", one with "8 days, 15 hours...". There is, however, other weird behavior related to first and second alert as well. If this can not be reproduced, I will have a look at my configuration. Thanks anyways for the effort!

Still cannot reproduce. Changing alerts on the iOS device co

Wed, 27 Nov 2013 01:22:26 +0000

Still cannot reproduce. Changing alerts on the iOS device correctly changes it on the server.

> Still cannot reproduce. Changing alerts on the iOS device

Wed, 27 Nov 2013 01:40:23 +0000

> Still cannot reproduce. Changing alerts on the iOS device correctly > changes it on the server. In the Mysql database I use, I mostly get the value 19804384 for event_alarm in kronolith_events. Initial event creation from IOS gives the value 0, then on any change on the client it changes to the 19804384 value.

On OSX 10.9, the OS calendar app does not introduce this bug

Wed, 27 Nov 2013 01:46:16 +0000

On OSX 10.9, the OS calendar app does not introduce this bug. It is just the IOS doing this. However, I can move entries to a later date on IOS without trouble, for example. It is just the alarm entry. If I view a OSX 10.9 created calendar entry with just one alarm, the IOS client shows the correct alarm time as a second alert, with a default alert at the time of the event.

Ok. I can reproduce now. This are the steps: 1) Create an

Wed, 27 Nov 2013 02:02:53 +0000

Ok. I can reproduce now. This are the steps: 1) Create an event on the client, while the default alarm setting is "At Time of Event". If this is not set, or the alarm is set to a different initial value it doesn't trigger the bug. 2) After event syncs, change the alarm on the client to a different value, such as "15 minutes" prior. WIll investigate further, but this sounds like a bug in iOS.

I can confirm this. Setting the default alert times to non

Wed, 27 Nov 2013 02:08:10 +0000

I can confirm this. Setting the default alert times to none in IOS makes the bug disappear. At least there is a workaround. Thanks again for your efforts!

Tested with Baikal server 0.2.6, which is also relying on th

Wed, 27 Nov 2013 02:29:32 +0000

Tested with Baikal server 0.2.6, which is also relying on the sabredav framework. It can handle the IOS default alert at time of the event.

iOS sends two alarms with the event. Baikal probably uses th

Wed, 27 Nov 2013 09:23:41 +0000

iOS sends two alarms with the event. Baikal probably uses the first one, which is correct, while Kronolith uses the second one, which is completely broken and senseless: BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:Erinnerung TRIGGER:-PT5M UID:9AF86893-DC43-4B41-BE3E-45D32D9046C1 X-WR-ALARMUID:9AF86893-DC43-4B41-BE3E-45D32D9046C1 END:VALARM BEGIN:VALARM ACTION:NONE TRIGGER;VALUE=DATE-TIME:19760401T005545Z END:VALARM We might want to simply ignore alarms with no action.

Changes have been made in Git (master): commit 9422ef8f18c8

Wed, 27 Nov 2013 09:39:32 +0000

Changes have been made in Git (master): commit 9422ef8f18c86220138c07d89738d856f4114da9 Author: Jan Schneider Date: Wed Nov 27 10:36:35 2013 +0100 [jan] Ignore iCalendar alarms without action, and use first, not last alarm (Bug #12865). Conflicts: kronolith/docs/CHANGES kronolith/package.xml kronolith/docs/CHANGES | 2 ++ kronolith/lib/Event.php | 7 +++++++ kronolith/package.xml | 2 ++ 3 files changed, 11 insertions(+), 0 deletions(-) http://git.horde.org/horde-git/-/commit/9422ef8f18c86220138c07d89738d856f4114da9