Sync issue with darwin calendar server

[WhyNotHugo]

This issue was moved from the issue tracker at GitLab.

---

I am trying creating a todo and then syncing it with darwin calendar server.
That fails with following error from darwin calendar server:

2016-04-15 02:55:17+0300 [-] [caldav-1]  [-] [twistedcaldav.method.put_common#error] Invalid calendar data: Calendar data had unfixable problems:
2016-04-15 02:55:17+0300 [-] [caldav-1]           [VTODO] Missing or too many required property: DTSTAMP

What I did:

1. I installed current version of todoman with pip.
2. Set up sync with darwin calendar server with vdirsyncer. Setup works (I can sync calendar/todo items, edit todos created from other sources, etc).
3. Tried to create new todo with following line: todo new -l calendar "test todo"
4. Todo is created locally and can be seen/modified
5. Sync fails with quoted error in server logs.

Resulting file (and file with same summary, but created from android "tasks" application, that syncs successfully are attached.
fail.ics
success.ics

The successful one does contain DTSTAMP field.

[WhyNotHugo]

Indeed, it looks like DTSTART is a required field for VTODO entries, however, RFC5545 doesn't seem to specify what it should contain (and there's no coherent value I can think of either).

I'll try to look into this.

[untitaker]

DTSTAMP vs DTSTART.

[fhunter]

I found it here: http://www.ietf.org/rfc/rfc2445.txt and in RFC5545 in part: 3.8.7.2. Date-Time Stamp

Property Name: DTSTAMP
Purpose: The property indicates the date/time that the instance of
the iCalendar object was created.

[WhyNotHugo]

Sorry, I mixed up DTSTAMP and DTSTART. It makes sense now.

[untitaker]

I wonder if we could make the case that icalendar should generate DTSTAMP implicitly. Otherwise it would create invalid iCalendars by default.

On 17 April 2016 14:24:14 CEST, Hugo Osvaldo Barrera notifications@github.com wrote:

Sorry, I mixed up DTSTAMP and DTSTART. It makes sense now.

---

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#15 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[WhyNotHugo]

I've created collective/icalendar#193, to see if this can eventually be fixed upstream.