The latest update of TaskTask, 3.2.492, just landed in the App Store tonight. I thought this would resolve all of the issues people have been running into where TaskTask won’t connect to their server with the 3.2.x update but previously did. However, shortly after the update went live, Nick S. reported an issue that he could no longer connect to his Exchange 2003 server which required “Allow Invalid Certs” to be enabled (and was enabled).
Turns out, the update that fixes the ability to connect to some servers breaks the ability to connect to others. I’m flustered that somehow I missed this when I was producing the update for the first issue. I’ve created a fix that resolves both issues, QA tested it against Exchange 2003, 2007, and 2010 servers with valid and invalid certificates, and just now have submitted it to the app store.
In the mean time, if you have an account configuration that requires you to turn on “Allow Invalid Certificates” I recommend you do not upgrade TaskTask to 3.2.492, since TaskTask will stop being able to connect to your server. If you do upgrade, you will see an error message that includes “errSSLXCertChainInvalid” at the bottom, which indicates that your SSL certificate is invalid/self signed and TaskTask failed to ignore the bad certificate.
All of this unfortunately started because of a change in the way SSL connections are configured when an application is built using the iOS 5 SDK. The coming update, 3.2.494, will resolve these connection issues and should get everyone back on track.