Windows Phone 7 users in the cold after Twitter changes

Tweeting from your Windows Phone? You might want to avoid signing out, according to reports circulating on news sites. Users are reporting their favorite Twitter apps have started throwing up errors, a problem that seems to have begun sometime yesterday.

WPCentral is reporting that a minor change in the Twitter API has been hitting Windows Phone 7 users looking to get their tweet fix on the move. The problem? Most WP7 apps rely on the Hammock library, a popular tool used by Twitter apps to access the service. This minor change has confused Hammock; in turn a wide range of Twitter apps have been hit.

The more technically minded will be pleased to know that there's an ongoing discussion on the developer forums to try and get to the source of the problem. The problem appears to be on Twitter's end, but the Hammock developers and other Twitter app writers are working away to find a solution.

For now, advice seems to be to avoid switching accounts or signing out. The sign in process seems to be causing the most problems for people, with the authentication process failing.

Have you noticed anything unusual on your device? Let us know in the comments.

Report a problem with article
Previous Story

No Android 4.0 update for Galaxy S and first Galaxy Tab

Next Story

Republic Wireless offers unlimited use for $19 a month

21 Comments

Commenting is disabled on this article.

The title makes it sound as if it is Microsofts fault and that it is a flaw in the OS. I am sure a lot of other clients had to be recoded to support the new API.
Tweeter should of known better before they retired the old service. This is cowboy dev on behalf of tweeter

If Microsoft broke the Silverlight API like this, the screaming from the developer community would be justifiably LOUD. But when Twitter breaks their API, everything is MUM.

KingCrimson said,
If Microsoft broke the Silverlight API like this, the screaming from the developer community would be justifiably LOUD. But when Twitter breaks their API, everything is MUM.

Presumably because the apps still work, and you can still use the built-in Twitter integration. It's only adding new accounts to third party apps that is the problem.

what said,

Presumably because the apps still work, and you can still use the built-in Twitter integration. It's only adding new accounts to third party apps that is the problem.

So devs are expected to just stop having new users download and use their apps? Because it isn't at all important to a dev that NEW USERS are able to add to their user base. /sarc

SiLeNtDeAtH said,
So devs are expected to just stop having new users download and use their apps? Because it isn't at all important to a dev that NEW USERS are able to add to their user base. /sarc

Chill bro, I'm only suggesting why there might not have been a huge uproar over it.

You never know, maybe WP7 devs are generally more humble human beings.

_dandy_ said,
Is it fair to bring up "...and nothing of value was lost"?

Suddenly users have a bad impression of Windows Phone because Twitter integration is broken. That translates to huge losses for Microsoft and OEMs.

KingCrimson said,

Suddenly users have a bad impression of Windows Phone because Twitter integration is broken. That translates to huge losses for Microsoft and OEMs.

Only twitter app dont work, it works fine in people hub which is integrated in WP7

I really want an updated twitter app that is in line with the current changes to the twitter layout. But....oh well. I can dream, can't I?

This specific issue started overnight on the 21st. Apps that use the Hammock REST library were affected.

When apps would attempt to grab an auth token when users tried logging on, the response being sent back by Twitter was suddenly gzipped - a change that was not previously announced and may or may not have been intentional on Twitter's side.

The work around is to alter how the response is handled and unzip it before trying to grab the oauth token out of the response Content.

SiLeNtDeAtH said,
This specific issue started overnight on the 21st. Apps that use the Hammock REST library were affected.

When apps would attempt to grab an auth token when users tried logging on, the response being sent back by Twitter was suddenly gzipped - a change that was not previously announced and may or may not have been intentional on Twitter's side.

The work around is to alter how the response is handled and unzip it before trying to grab the oauth token out of the response Content.


thanks for the insight. Very good post.

FalseAgent said,

thanks for the insight. Very good post.
Thanks - it was easy though. One of my apps is affected and I've been stressed about this for 2 days now so I am close to issue. :-)

I have imlpemented the fix and have a submission ready for the Marketplace, but the day this all started (and before I knew there was an issue) I submitted an app update to correct a spelling error. So now I have to wait for that update to either get rejected or published (it should get rejected given the issue) before I can submit the update to work around this issue. Essentially, it will be around 2 weeks before this fix is in place for me. So any new users are going to think my app is crap until then. AWESOME Christmas present. /sarc

And all the while, *crickets* from Twitter, aside from a "we're looking into this" post yesterday morning on the discussion thread about the problem.

I've heard it works fine when using the people hub. Better off using what's built in, the less 3rd party stuff the better.

Twitter want more people using the website or official app don't they, im sure I've seen articles related to this before...

I noticed I was not able to sign into my account almost as soon as the new update to Twitter started to roll out, maybe two weeks ago. It really did not bother me that much because I have my twitter account linked into my social connections within my phone.

For the app, I am still unable to login. Rather rubbish if you ask me.