Hi Guys
We’re seeing a fair number of reports about Twitter authentication getting stuck recently. We’re currently investigating these reports, and will be shipping a couple of fixes as part of the 1.0.2 update. We don’t have a date for 1.0.2 yet, however we’re working on it currently.
We’d like to thank all those who’ve sent in Console logs to help us identify the issue.
Kind Regards,
Nik
Hi Guys - just a quick update on this issue.
We’ve taken a look at the Console logs sent in by a number of folks, and determined the cause of the problem. Currently, Socialite connects to Twitter using SSL (a secure connection). For some reason, the secure certificate for Twitter.com is either not ‘trusted’ on users’ systems, or invalid. If you were connecting to the Twitter URLs we’re using in Safari, you’d be prompted accept the SSL certificate or not. As we’re using the underlying networking in OS X, there’s currently no UI to accept the SSL certificate.
We’re going to be moving away from SSL for all bar the absolutely necessary API calls (to verify your account details) in the next version of Socialite, and this should hopefully fix up your issues.
We’re still working on a number of other improvements to Socialite for the 1.0.2 release, however as soon as it’s ready for testing we’ll be sure to post a beta so that folk can confirm that our fixes do indeed cure this issue.
Thanks for your patience in this matter,
Kind Regards,
Nik
Twitter’s certificate is assigned to “twitter.com”, so it only comes up as invalid if you use “www.twitter.com”.
So, in essence, users are stuck with a broken segment of the app until another release? Can’t a patch be made available? Seems a shame to pay for something and be required to use another vendor’s product…
I don’t get that either… the “patch” for the flickr-problem took only, what, 24-48 hours? And without having checked the facts: unkn0wnvariable posted the solution in here.
If he’s not right, it would at least be nice to hear from the developers what actually goes wrong with the Twitter auth.
Delivering buggy/not working software without further “real” information on when a fix is to be expected, etc, , is somewhat Microsoft-y. 
Hi Guys
The patch for the Flickr problem was a simple one-line code change that, once we had a new API key from Flickr, was quick and easy to implement. This issue has required a little more investigation and fixing - and the changes made to the Twitter authentication are also improvements that we’ve added to the Flickr / Facebook side of things. As the 1.0.2 release also has a few other tweaks and improvements it’s not something we’re able to fix overnight!
Whilst unkn0wnvariable did indeed post some further information, the issue wasn’t solely isolated to SSL errors - if a network connection timed out, it would also cause this issue. (and the 1.0.2 release includes a number of network robustness improvements).
As has been mentioned elsewhere in a few other threads, we’re going to be releasing Socialite 1.0.2 later this week.
Thanks for your patience and understanding,
Nik
I only lose Twitter if the network isn’t there when Socialite starts. All services bring up the authentication pages but after the connection is restored, and the app restarted, they all come back to life except Twitter.
That one has to be removed and re-added.
Not sure if that’s the issue you’re referring to.
Hi Monty,
Have you tried removing the Flickr and Facebook services from Socialite and then removing the Socialite application permissions from Flickr and Facebook themselves?
For Flickr.com go to:
You -> Your Apps -> App’s You’re Using
..and for Facebook.com go to:
Settings -> Application Settings -> Show: Authorised
Then re-add the services in Socialite. Does this resolve the issue?
Kind regards
Luke
