{"id":9253,"date":"2014-02-15T21:25:07","date_gmt":"2014-02-16T05:25:07","guid":{"rendered":"http:\/\/www.perivision.net\/wordpress\/?p=9253"},"modified":"2014-02-20T19:12:14","modified_gmt":"2014-02-21T03:12:14","slug":"your-twitter-app-suddenly-does-not-work-with-oauth-could-be-your-database","status":"publish","type":"post","link":"https:\/\/www.perivision.net\/wordpress\/2014\/02\/your-twitter-app-suddenly-does-not-work-with-oauth-could-be-your-database\/","title":{"rendered":"Your Twitter app suddenly does not work with OAuth, could be your database"},"content":{"rendered":"

\"twitter64\"<\/a>A few days back one of my twitter aps, NewsSnacker.com stopped working for some reason. I have not touched the code in months.\u00a0 So what the heck was going on?\u00a0 More odd is that fact the twittFilter was working fine.\u00a0 They are based off the same OAuth2.0 code.\u00a0 After a few hours of hacking and dropping trace statements all over the place, I figured it.<\/p>\n

I had a quick look at the Twitter blog to see of there was any warnings of something new with the API.\u00a0 Nothing jumped out at me but I did notice that something was changing from 32 bits to 64 bits.\u00a0 I did not pay it much mind.\u00a0 As I was debugging I finally decided to get the keys from the twitter site and manually start making some calls. The site started working again.\u00a0 What the heck?\u00a0 I checked my SQL statements and I was getting data from the database.\u00a0 Then I looked at the last 4 digits just to see of perhaps my tokens got corrupted or something.\u00a0 They do not match!\u00a0 For the first 4 digits DO match!\u00a0 Then it stuck me.\u00a0 I quickly logged into the database and yup, just as I thought.\u00a0 I had my fields set to textvar fields set to 40 charters.\u00a0 Default.\u00a0 Arrggg.. All this work and it was just the keys getting larger.<\/p>\n

I changed to token fields to 64 each and everything started working again.\u00a0 Well mostly again because I introduced new errors and founds some weakness in the codes that I never noticed before.\u00a0 That was one afternoon shot to hell.<\/p>\n

So if you suddenly find your twitter app is not working anymore, check you database schema, could be a quick fix and save you a few hours.<\/p>\n

Related Posts<\/H3>