CALDAV verification fails with iOS.

[mjoaquim12]

CALDAV stopped working on iPhone. Works well on other clients.

[bradmac]

please provide details.

[mjoaquim12]

The two step authentication process fails for iOS CalDAV account. The first request is processed but no subsequent request with auth details is received.

iOS 12.1.4 error logs with production URL:

error	11:39:36.914815 +0400	accountsd	"<private> is trying to verify account credentials for account: <private>"
error	11:39:36.916537 +0400	accountsd	CredStore - performQuery - Error copying matching creds.  Error=-25300, query=<private>
error	11:39:37.464118 +0400	accountsd	CredStore - performQuery - Error copying matching creds.  Error=-25300, query=<private>
error	11:39:38.089785 +0400	Preferences	validation failed with error Error Domain=CoreDAVErrorDomain Code=8

iOS 12.1.4 error logs with development URL:

error	11:33:51.451997 +0400	accountsd	"<private> is trying to verify account credentials for account: <private>"
error	11:33:51.453017 +0400	accountsd	CredStore - performQuery - Error copying matching creds.  Error=-25300, query=<private>
error	11:33:51.544240 +0400	accountsd	CredStore - performQuery - Error copying matching creds.  Error=-25300, query=<private>
error	11:33:51.544845 +0400	accountsd	Cancelling authentication challenge for insecure connection using basic authentication for URL <private>
error	11:33:51.547042 +0400	Preferences	validation failed with error Error Domain=DAAccountValidationDomain Code=102 UserInfo={NSUnderlyingError=0x283c0eeb0 {Error Domain=NSURLErrorDomain Code=-1012 UserInfo={NSErrorFailingURLStringKey=<private>, NSErrorFailingURLKey=<private>}}}

Stackoverflow says:
https://stackoverflow.com/questions/46099940/credstore-perform-query-error/46806008#46806008

[HasanGee]

Hello, has this issue been resolved? We are experiencing the same issue.

[bradmac]

Hey guys, the ios logs above really dont tell me anything.

I really need to see some logs from the milton side.

And the first thing you should do to debug is to check the network logs. Ie what status codes is milton returning for each request? Any error codes at all indicate an incorrect implementation and will cause the operation as a whole to fail.

Eg check for 500's, 401s, 404's, etc

If you're seeing an error response code then try to find out why. A very common problem is that developers just ignore required semantics they dont understand or dont see a need for, but OS clients tend to be sensitive to edge cases.

I dont think the SO link above is relevant.