[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Inf-IT DAVcl] Android synching problem (again)


Hi Johan and Marten,
can you send me that file too?
I can check if something goes wrong.
I repeated every step for creating such situation in our CalDavZAP, but I get same UIDs.
Thanks,

Andrej
Dňa 5. 3. 2014 9:45 Marten Gajda wrote / napísal(a):
Hi Johan,

the file you sent me is definitely broken. It contains two VEVENTs with different UIDs, which is not allowed in CalDAV:

BEGIN:VEVENT
...
UID:8xgll0ja-tmwa-uubj-n5fo-cnngv7hgkx5w
....
END:VEVENT
BEGIN:VEVENT
...
UID:jgp2g2m2-yc1t-bgl4-817g-s3ynu2aub2sr
...
END:VEVENT
PRODID:-//Inf-IT//CalDavZAP 0.10.0.2//EN

How exactly did you export/download that file?

@Ján can you check how that could happen?

cheers

Marten

Am 04.03.2014 20:38, schrieb Johan Vromans:
Setup: DAViCal server on NAS.
CalDAVzap on linux client.
Business Calendar Pro + CalDAVsynch on Samsung Galaxy Note 2 10.1.
Business Calendar Pro + CalDAVsynch on Motorola Moto G.
iPad with standard iPad calendar.

The appointment is a repeating event, to repeat every two weeks.
Starting tomorrow. Ending 2014-12-31. The appointment exists on all
clients. It is displayed in weeks 10, 12, and so on.

Using CalDAVzap I edit the first occurrence of the appointment and
change all occurrences: change the starting date to one week later. It
is now displayed in weeks 11, 13, and so on.

The change is picked up correctly by the iPad.

The Samsung now shows the (new?) appointment in weeks 11, 13, ... but
still shows the (old?) appointment in weeks 10, 12, ...

The Motorola doesn't show either appointment.

Unfortunately I was just a little too late to intercept the log file.
I'l try to be more quick if something like this happens again.

-- Johan





References:
[Inf-IT DAVcl] Android synching problem (again)Johan Vromans <jvromans@xxxxxxxxxxx>
Re: [Inf-IT DAVcl] Android synching problem (again)Marten Gajda <marten@xxxxxxxx>