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.
December 1, 2011 at 4:16 am
No help from latest update, still not syncing. When should we expect this to be resolved, easiest way is to do roll back to previous version which worked for all.
November 30, 2011 at 12:17 pm
Setting up the account I get a error message while connecting to exchaneg server. Before I installed the update evreythings worked fine !!
After the update I was not able to connect to my tasks.
Unfortunately the new apple task app works without any problem !!
Hopefully the next update solves the problem. Right now I’m angy about the situation and the update practise.
Elmar
November 30, 2011 at 5:49 am
as of 11/30/11 it appears that the issue is still unresolved? Or should we attempt to upgrade yet?
November 29, 2011 at 12:15 pm
Now it Works again !!! Many Thanks!!!
November 29, 2011 at 11:21 am
Update doesn’t work for me. I bought this app yesterday (didn’t see the problem notes). Still get a message “invalid request”, could not detect your server settings, and has not yet synced with Outlook.
November 28, 2011 at 5:49 am
Hi,
Any ETA on this fix please?
Many Thanks,
Scott.
November 25, 2011 at 9:44 pm
I unfortunately updated the app and now can’t sync.
How far away is the new version? I use TaskTask a lot and am now sort of lost without it and am starting to wonder if ‘Reminders’ is worth using.
Please post an update.
November 25, 2011 at 6:22 am
Hi guys,
I was having the same issue and we’re using Exchange 2010. I deleted the cache on the app and synching started working again.
Thanks,
Keith
November 24, 2011 at 3:34 am
This is a fantastic app and I feel lost without it. Guess I should have read the cautionary note before pressing the update button. I look forward to the next release – in the mean time I will continue to struggle with Reminders.
November 24, 2011 at 12:08 am
Before installing version 3.2.492 there were no problems with Exchange 2010, despite IOS5.
Now I get the error message!
I ask for a quick!! fix or short-term opportunity to downgrade.
This is so important because the app is very good.
November 22, 2011 at 1:24 pm
How To downgrade??? I need having sync with my exchange everytime!! Hurry up. Please
November 22, 2011 at 11:18 am
Hi,
This also holds true with Exchange 2007 as well.
Till you resolve this issue, isn’t there a way to re-download the older version?
When can we expect the new update?
Thank you
Mohamed