secure connection failed
For a few weeks now, some users have been seeing a "secure connection failed" error. A bunch of us Twitter client developers and the very kind folks at Twitter have been trying to track down the problem - so far with no success.
All we know is that it seems to affect all iPhone Twitter clients that connect to Twitter securely (via SSL). Oddly enough, it seems to *only* affect clients running on iPhone. (If you notice it happening on a desktop client or on Blackberry or Android, please let someone know - it would be very helpful). Update: Got reports of it happening on Mac and Pre as well. If you notice a lot more complaints about it happening on Tweetie (and on iPhone), it's probably because Tweetie and Twitter on iPhone are more popular than using Twitter on any other platform (more people hitting the bug).
It happens on WiFi, EDGE, and 3G. The OS version doesn't seem to matter. And it's not easily reproducible, making it very hard to debug. It *seems* to have started after the most recent DDOS against Twitter, but this may be coincidence.
While we're all pulling out our hair, I've heard from a few people that you can do a few things that help a little bit:
1. When you get the error, try refreshing a few times. It might just go away.
2. Try logging in to Twitter via Safari (make sure you go to the HTTPS version: https://twitter.com). Then try using Tweetie (or your other client of choice).
3. If you figure out some magic combination of network settings, account settings, standing on one leg, and proper incantation where you can reproduce the problem consistently - let me (contact@atebits.com).
Sorry about this - hopefully it will get sorted out soon.
Update:
More details: http://code.google.com/p/twitter-api/issues/detail?id=971