iOS 5.0.1 CalDAV account "Unable to verify account information."

[supergillis]

Hi,

I'm trying to get sabredav working on an iPad 2 with iOS 5.0.1 but it's not really working...

CalDAV works fine on iPhone 1 with iOS 3.4 (?) but it doesn't work on the iPad 2.

I really have no idea what the problem might be. Here are the HTTP logs:

PROPFIND principals/username
<?xml version="1.0" encoding="UTF-8"?>
<A:propfind xmlns:A="DAV:">
  <A:prop>
    <A:current-user-principal/>
    <A:principal-URL/>
    <A:resourcetype/>
  </A:prop>
</A:propfind>

RESPONSE
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:cal="urn:ietf:params:xml:ns:caldav" xmlns:cs="http://calendarserver.org/ns/" xmlns:card="urn:ietf:params:xml:ns:carddav">
  <d:response>
    <d:href>/principals/username/</d:href>
    <d:propstat>
      <d:prop>
        <d:principal-URL>
          <d:href>/principals/username/</d:href>
        </d:principal-URL>
        <d:current-user-principal>
          <d:href>/principals/username/</d:href>
        </d:current-user-principal>
        <d:resourcetype>
          <d:principal/>
        </d:resourcetype>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
</d:multistatus>

After communication with the server the new account dialog returns an error message "Unable to verify account information."

Anyone knows what to do?

Thanks in advance,
Gillis

[Evert Pot]

Hi Supergillis,

Nothing looks wrong this particular response. I suspect the problem is in a different castle.
Is it possible for you to make a full recording using Charles HTTP proxy, and send this over (you can send it directly to my email, in case there's private data).

Let me know,
Evert

[supergillis]

Hi Evert,

Thanks for your fast response! I only have access to the iPad at work so I will send you the HTTP logs tomorrow!

Thanks in advance,

Gillis

[supergillis]

Okay, I found out the problem!

I didn't have the ACL plugin enabled because when it was enabled it didn't give the correct permissions for my calendars and contacts. Because the ACL plugin was enabled, it didn't respond to the new request of iOS 5+.

The permission problem is fixed now. My calendar and contacts info returned a principal URI with a trailing '/' that caused a problem DAVACL::Plugin::getCurrentUserPrivilegeSet. After removing the trailing '/', everything works out just fine.

Thanks!

[Evert Pot]

On Sep 17, 2012, at 12:31 PM, supergillis <super...@gmail.com> wrote:

> Okay, I found out the problem!
>
> I didn't have the ACL plugin enabled because when it was enabled it didn't give the correct permissions for my calendars and contacts. Because the ACL plugin was enabled, it didn't respond to the new request of iOS 5+.

Ah good to hear. I can totally see how it may seem that the ACL plugin is an optional thing, but it's really required :)

Evert