Comment 10 for bug 1261191

I have similar behaviour on ubuntu touch since OTA-13 (vivid), but i don't know if this bug involves also phones or it's another story. However in my tests (with google calendar) i found this:

a) if i set an event with defined time (eg. from 09:00 am to 10:00 am) indicator works always as expected;

b) if i add an event for the whole day (one shot) indicator reports correct date and time 00:00;

c) if i add an event for the whole day yearly repeated (eg. birthday), indicator reports wrong values, always a day ahead, with this particularity:
   - If notification is turned off the time is 00:00;
   - If notification is set (any value), the time is always 02:00 am

If i tap on the wrong date, calendar opens on (indeed) the wrong date, which doesn't have events registered, but in calendar and in agenda events are correctly registered.

Analyzing the ical file for both b) and c) cases, i can see that the only difference between the two files is the RRULE:FREQ=YEARLY statement.

ical snippet for case b) is:

DTSTART;VALUE=DATE:20170413
DTEND;VALUE=DATE:20170414

ical snippet for case c) is:

DTSTART;VALUE=DATE:20170413
RRULE:FREQ=YEARLY
DTEND;VALUE=DATE:20170414

Maybe it's a different case, but i have both DTSTART and DTEND correctly(?) set. It seems that there is something wrong in parsing the RRULE statement. I tried also to play with google parameters, but the only that highlights the problem is the repetition of an event. Doesn't indicator expects the DTEND closely after DTSTART in the ical file?