Benches iPhone

3

Caldav read-only?

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

When iPhone OS 3.0 was released, the Caldav support was great. I connected it to my davical server, and it synced perfectly. Events created on my phone showed up on my desktop calendar. Events created on my desktop calendar showed up on my phone. Life was bliss.

Tuesday I upgraded the phone to OS 3.1. Today I noticed the access to the caldav calendars is read-only. I can not change existing events in the caldav calendars on the phone, and I can not create new events in those calendars.

It had been a while since I had updated any calendars on the phone, so I'm not positive the 3.1 upgrade is what broke it. It might have been broken before the upgrade. But the upgrade is the only significant change since I originally had it working.

Any ideas?

3 replies

Sign in or join Beachball Help to reply.

  1. 0

    Simpsomatt

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I found my answer. There's a message about it on the davical list. The developer is aware of the problem. I don't completely understand the explanation, but apparently a new release of davical is forthcoming which will make everything better again.

  2. 0

    ericg_7

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, it was iPhone 3.1 that borked write access to davical caldav calendars. Glad to hear the Davical developer is fixing it. I will scoot over there and see what's up.

    On the bright side, the "year 2145" bug on iPhone with events created by certain other caldav clients "seems" to have been addressed.

    Sheesh! What a soap opera. All for the sake of shared calendars. Any wonder the iPhone has not made a dent in the Enterprise world?

    PS.. just noticed they don't have an "iPhone OS 3.1" choice yet in the OS dropdown box. Maybe there's a lesson there.

  3. 0

    ericg_7

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Just to confirm, I have just updated to DaviCAL 0.9.7.2 on Debian Sid (sidux, actually) and it does indeed fix the problem. No worries, and thanks a bunch to Andrew McMillan, the developer. Apple should have him on the payroll!