Hello, There are no such restrictions. Theoretically, you can sync hundreds of calendars, so I guess there’s another reason why some calendars don’t show up. Do those calendars have something in common, for instance are they shared calendars?

@wanderlei-huttel I see, sorry… didn’t notice the logs. It doesn’t look suspicious from DAVx⁵ point of view.

@6042114fa0 I have found emails where this was reported … but very rarely.

@zstephen said in Calendar items in phone are synced then will change time: Intermittent problems are the worst, I’ve always disliked them. That’s true… Is there any way I can verbosely see the calendar event details in logcat mode? I can try to pinpoint this log payload in my own calendar where I am seeing this issue by looking for that event name in the sync log files. Yes, when you turn on DAVdroid logging, all synchronized events will be logged, including date/time/time zone and name, so you can then search for the names. I guess it maybe somehow related to the time zone… maybe it happens only for events when DST is (in)active or around the DST change? However, the best thing would be to turn on DAVdroid logging and leave it on until the problem occurs (will take some space). Then every required information should be in the logs.

Hello, Are you sure this problem is related to DAVdroid? DAVdroid just shows the events from subscribed calendars, regardless of whether the calendar is shared or not. So, as soon as the server sends the events for the shared calendar, they should show up in DAVdroid. If they do not and there is no error message, it’s probably this server problem.

I just found that while the shared calendars can’t be viewed and thus not edited…Where read/write access to the shared calendar applies, calendar events can be created in the shared calendar on the phone and are shown in the Zimbra web based calendar after sync completes.

@tvamosi As far as I know, Zimbra uses calendar-proxy-read/write for CalDAV delegation, which is understood by DAVdroid. As far as I know, there’s no approriate equivalent for CardDAV (address books). Other possible mechanisms would be a group principal membership, but that’s currently very wide-spread. Short answer: It’s a CardDAV limitation.

Hello, you’re welcome What version of zimbra do you use? Can you provide a test accounts or send us logs? Otherwise we cannot reproduce this. Our zimbra test account works fine.