Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.6: A fix for iCal not logging into certain Caldav servers' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: A fix for iCal not logging into certain Caldav servers
Authored by: ars on Apr 26, '10 09:34:37AM

I use Google's caldav to synchronize an Ical calendar on 3 machines: an Imac running Snow leopard, a macbook pro running leopard, and an iPod Touch. I have not had a single issue with calendars not being found. I can enter a calendar appointment on any of the three machines and it shows up on the other two automatically.



[ Reply to This | # ]
10.6: A fix for iCal not logging into certain Caldav servers
Authored by: robleach on Apr 26, '10 12:37:56PM

I too sync google calendars in the same way with 4 machines, an Intel Mac Pro running 10.5.8, an Intel macBook running 10.5.8, a G4 PowerMac running 10.5.8, and an Intel Mac Mini running 10.5.8. And as I said, all successfully update. I too can enter a calendar appointment on any of the 4 machines and it shows up on the other 3 automatically. However, I get these incessant, seemingly meaningless errors, as do many others. I'm glad you're not getting the errors, but perhaps you're not utilizing the same combo of features or testing the limits via complicated recursions or whatever - noone knows what's causing it. I have 20 calendars from about a dozen different collaborators as well as my own set of over 26 subscribed and published calendars of my own going through MobileMe and icalx.com. Using google calendar was a recent change in the setup because I wanted others in my group to be able to edit the calendars, however since then, I've had to deal with these incessant errors. I'd get rid of google's caldav feature if I could, but right now I'm dependent on it so I just click the error windows every 5 minutes or so. I've read up on the issue on many forums. It's a known issue with some implementations being tracked in google code, but the cause has not been determined.

Edited on Apr 26, '10 12:40:08PM by robleach



[ Reply to This | # ]